Help

Help›Mail›Draft and send an email

Draft and send an email

Reviewed Sep 7, 2026

View as Markdown
Words
TierPro
SeatA person on Tightly Pro whose organisation holds the email agent, with a connected mailbox, on a seat that may write
Ask TightlyMay propose it; you press

What it writes ​

Two acts, and only the second writes anything that leaves. Drafting composes a note from a record's own read to a person the record holds: a purchase order to its supplier, or one season of an account's order book to its buyer, or a commitment. The recipient comes from the record's contacts, never a typed address; the words are the house template filled with figures the reads served, each kept with the read it came from; the attachment is what the record offers. Drafting sends nothing and can be asked as often as you like.

Sending takes the draft out through your own connected mailbox, so the mail leaves under your name and never under a shared identity. It spends nothing and moves none of a Commitment's five declared numbers. A note about a purchase order is filed against that order's thread, so the reply lands on it, and the note carries the act it came from.

Who may press it ​

A person on Tightly Pro whose organisation holds the email agent, with a connected mailbox, on a seat that may write. Composing is open to a read-only seat, which can write itself a note and never send one. The chip Ask offers is a door: it opens the email drawer over the page you are on, and the drawer's own Send is the act, so the page performs. Ask never sends from a chat and never adds this act to its own allowlist, and a key never sends. The email agent proposes and drafts and never sends either.

Ask offers the draft only where a mailbox is connected and the seat may send; otherwise the suggestion is not drawn. There are caps: fifty sends a day per person through Ask, three to one recipient in seven days without a reply from them, and a do-not-email list per organisation. A send the caps refuse keeps the draft.

What you see ​

The drawer is titled Note to {name}, with To, Subject, Note and Attached. To offers only the record's own people. In the note the served figures are dotted-underlined, with Yours · Ask on hover, so what a read produced is told from what you typed. Subject and the note are editable while the note is a draft, the note through Edit and Done.

Send holds the note for thirty seconds before it leaves, and the server's receipt says so:

Sent from {mailbox}; take it back for {seconds} seconds.

While it is held the button becomes Take it back, beside Leaves in {n} seconds. Once the note has gone the record reads

Sent from {mailbox}; nothing comes back.

with the mailbox and the message id. Nothing pops up and nothing navigates away. Without a connected mailbox the drawer offers the door Connect a mailbox, which is Settings › Email.

What to do ​

The way back is Take it back inside the thirty seconds: the note returns to a draft, reads Taken back; nothing was sent., and can be edited or closed. After release there is none, and the record says so. A reply to a note about a purchase order lands on that order's thread.

Refusals you may read ​

No mailbox connected, served by the send route:

Email integration is not set up for this user and organization

The drawer's own sentences where the wire refused without words: "This note could not be opened just now.", "That change was not kept and no reason came back.", "This note was not sent and no reason came back.", "This note was not taken back and no reason came back." A server refusal with a sentence prints where the button was, character for character: a day's limit reached, a recipient written to three times without a reply, or an address on the do-not-email list each say so, and each keeps the draft.

Was this useful?