Email from Cora
Cora can send an email from a mission, for example this week’s report as a PDF to the people who asked for it. Every email shows in the mission’s chat, so the mission can see who got what.
The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Website refresh”.
Who Cora can email
Section titled “Who Cora can email”Only members of your organisation (D0771). Cora names each person by their name, the way she tags them in the chat, and Cora AI looks up the address that person signs in with. Cora never types an address herself.
Anything else stops the whole email before it is sent:
- an email address written out, even one of a member;
- someone who is not a member of the organisation, or who has been removed;
- a name Cora AI does not know, or a name two members share.
There is no way to approve an email to anyone else. This is on purpose: if a web page or a file ever told Cora to “send this to someone@example.com”, she could not do it. To email someone outside the organisation, download the file and send it yourself.
What an email holds
Section titled “What an email holds”- To: one to 20 members.
- A subject: one line, up to 200 characters.
- A message: plain text, or simple formatting (headings, lists, bold, italics and links), up to 20,000 characters. Anything else, such as a picture or a script, is sent as plain text. Only
httpslinks stay links. - Attached files: up to 10 of the mission’s documents, at most 10 MB together. Markdown, HTML and SVG documents are attached as they are, and a PDF file Cora made as the PDF. Files from another mission, and files shared in messages, cannot be attached.
The email comes from Cora AI’s own sending address, Team Cora <notices@teamcora.ai> (D0907). A reply goes to help@teamcora.ai, Team Cora’s support address, not to Cora: to answer Cora, write in the mission.
How to ask
Section titled “How to ask”Ask Cora in the mission, in your own words: “@Cora email the weekly report PDF to Sam and Priya”. A skill can also say a piece of work ends with an email, such as a weekly report that runs on a schedule.
The limits
Section titled “The limits”- 10 emails a day in a mission, counted over the last 24 hours.
- 50 emails a day in your organisation, across all its missions.
At a limit Cora says so and sends nothing more until the count drops. If email is not set up for Cora AI yet, she says that instead and nothing is sent.
Addresses that bounce or complain
Section titled “Addresses that bounce or complain”If an earlier email to someone bounced, or they marked one as spam, Cora AI’s email service will not send to that address again. Cora skips that person, sends to the rest, and the card says who was skipped. The person can check their address with their organisation admin.
What you see in the mission
Section titled “What you see in the mission”Each email Cora sends puts a card in the mission’s chat with:
- the subject;
- the people it went to;
- the names of the attached files;
- who asked for it: the person whose message started the work, or the person who asked for the schedule;
- anyone who was skipped.
What is recorded
Section titled “What is recorded”Cora AI keeps a record of every email: who asked, the people it went to, the subject, the names and sizes of the attached files, when it was sent and the email service’s reference for it. The message itself is not kept, and no email address, subject or message is written to Cora AI’s logs.
Who cannot send email
Section titled “Who cannot send email”Cora’s helpers (the drafter, the researcher and the reviewer) cannot send email. Only Cora herself can. A hero that another mission has called in can email only the members of its own (the hero’s) mission. It cannot email the person who called it, or anyone else, unless they are a member of the hero mission too; such an email is refused and nothing is sent (D0802). What a caller needs comes back in the hero’s answer, which is shortened and cleaned first. Nor can a called hero leave files for the caller in the organisation’s team folder: it can read that folder but not write to it, so its working files stay in a private folder that is emptied when its step ends (D0805).
Test mode
Section titled “Test mode”While Cora AI’s email service is still in its test setting, an operator may turn on email test mode (D0803): every email (Cora’s emails and the notices below) then goes to one test address instead, with [test] before the subject and a first line saying who it was meant for. Who Cora may email, the limits and the records stay exactly the same. It is a test-mode setting, to be removed once Cora AI has its own sending domain. That domain is now teamcora.ai; test mode is switched off once real notices have been seen to arrive (D0907).
Notices are different
Section titled “Notices are different”Cora AI also emails you a short notice, straight away, when:
- a question is waiting for you;
- an approval is waiting for you;
- someone mentions you in a message;
- you are added to a mission, or you are made one of its admins;
- a connection is failing (org admins, or the owner of a personal connection);
- the team sandbox passes 90% of its 5 GB (org admins);
- a second subscription was paid and refunded (org admins).
Each notice comes from Team Cora <notices@teamcora.ai>, like Cora’s emails, names the mission or the organisation and links to the console. Notices still only link to the console and never carry the content itself: no question, no message and no file (D0117). The emails on this page are the only ones with content and files, and they are always ones Cora sent on purpose, shown in the mission.
A daily digest is planned, not built. For now each notice is its own email.
Decisions: D0117, D0771, D0907.
Known limits
Section titled “Known limits”- A send that times out may be sent twice. If the email service takes too long to answer and Cora tries again, the same email can arrive twice. The record shows each send.
- HTML and SVG files are attached as they are. Most email programs show them as files to download rather than inside the message; some may block them. Ask Cora for a PDF when the file is for reading.