Simafri Suite

Takes a person out of a team. The threads they took from it stay on their name.

Gives a thread a subject that says what it is about, for the people who work it: shown in the lists and on the thread screen in place of the subject of the mail, and in "team_subject" of list_conversations and get_conversation. It is the team's label and never the subject of the correspondent's mail: "subject" stays the one they wrote, every answer still leaves as a "Re:" of it with the ticket number, and their mail client keeps the case as one conversation. Use it on a ticket whose subject says nothing of the request, a form notification ("New message from ...") or a bare order, once you know what is asked: name the request, not the person. One line, up to 255 characters; giving the subject of the mail again, or null, takes the team's away. The renaming is recorded on the thread as a note signed by the person this connection acts for, naming the former subject, and the search finds the thread by both. One subject per thread, so it takes one conversation_id.

Gives a team a new name. Its slug stays, so every reference to it keeps working.

Sends an answer in an existing thread, written by the caller, from the address the thread arrived through. A draft left pending on that thread is superseded, so the contact reads one answer. With "send_at" the answer is scheduled instead, and supersedes that draft only when it leaves.

Moves a thread of a mailbox into its Spam folder, where it stays readable and can be taken back out, and blocks its sender: their next message is filed in Spam too, without anybody being asked again. Spam is emptied 30 days after a thread lands there, and that deletion is final. Threads of a helpdesk queue have no Spam folder and are refused: file_conversation with "trash" throws them away instead. To report several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.

Writes down a message being prepared, so it can be finished later from anywhere. Pass "from" to start one; pass its id to write into it again, where the fields you leave out keep the value they had. Saving sends nothing: send_email is what sends.

Finds the threads of one mailbox by their subject, their text, the people on them or the names of the files they carried, best answer first. Call list_sender_addresses to find the box. This is how you look a mail up when you know a word of it and not where it is.

Writes and sends an email to someone, and opens the thread their answer will land in. The text goes out as given, so this is the tool for a message a person has read and approved. With "send_at" it is scheduled instead: nothing leaves until then, and list_scheduled_sends shows it waiting.

Says whether a thread of a mailbox leaves the Inbox for the Archive as soon as the box answers it, whether the answer is written in the webmail, through these tools or in a mail app such as Thunderbird. The thread comes back to the Inbox when a new message arrives in it. A setting of the box: on a box held by several people it moves the thread for all of them. A helpdesk queue refuses it, its threads being worked by status.

Says whether an incoming message has Iris draft an answer on its own. With it off, a draft is written when someone asks for one from the inbox, which is what keeps the model spend where you put it.

Says where a thread stands, and optionally where it stands in the pipeline. Both are recorded as decided by a person, so a later reading by Iris keeps them. To set the same status on several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.

Writes the block that closes what is written from an address. It belongs to the address, so everyone who writes from it signs the same way; it is put into a message when one is being written, not added behind the sender back.

Takes the name off a thread: nobody is handling it, and it goes back to the queue for whoever picks it up. It closes no door, the thread having been readable by everybody working that queue the whole time. Replayed on a thread nobody had taken, it answers the same thing. To give several threads back to the queue, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.

Lets an address write to the Inbox again: their next message is filed like anybody else's. Threads already sitting in Spam stay where they are, a block having always been about the mail still to come; file_conversation with "inbox" is what brings one of them back. An address this account holds no block on answers that there was nothing to lift.

Leaves the mailing list a thread came from (a newsletter, a promotional mailing, a notification list), in the name of the mailbox it arrived in, with what the last message received in the thread offers: one POST to the list's unsubscribe address when it accepts a one-click unsubscription, otherwise a short mail from the box to the list's own address. get_conversation says, in "unsubscribe" on each message, whether it offers a way out ("one_click", "mailto") and when the box took it ("done_at"). Call it once the person has said they want to leave that list: it is their decision about the mail they receive. The answer is {status, method, detail}: "unsubscribed" when the list took the request, "already" when the box had already left from that message (nothing is sent again), "not_offered" when no message of the thread offers a way out, and "refused" when nothing was done, with why in "detail". A thread filed as spam, and a sender that failed DMARC, are refused on purpose: unsubscribing from spam tells its sender that the address exists and is read, and report_spam is the gesture for those. A list that answers with an error is refused with its HTTP code.

Writes the fiche fields you pass, and leaves the others as they are. What is written here is recorded as coming from a person, which keeps a later reading by Iris from overwriting it.

Renames a folder a person made, moves it under another one or to the top, or both; the folders under it follow, and the threads in it stay. What you leave out keeps its value.

Writes a doc whole, keeping the previous version dated in its history. Send the title and the content each time, plus the brands and addresses it applies to.