Email threads
Threads synced from users' connected mailboxes, and how they link to records.
When users connect their Gmail / Google Workspace, Microsoft 365, or company mail (IMAP/SMTP) accounts, their emails sync to the CRM. Messages on the same subject are grouped into a thread (thread). A thread links to a company and, optionally, to a project, and appears in the Emails section on the cards of the related records.
Linking rules
- If the other party's email address matches a person's, the thread links to that person's company. If it doesn't, the company is found from the domain, or (depending on the organization's rules) a prospect company and person are created automatically.
- The project is chosen from these sources, in order: the reply chain, the first message sent from the CRM, the company's only open project, a quote / project number in the subject, and the company's most recent project (as a suggestion). The reason for the choice is in the
opp_howfield. - Users can move a thread to another project, link it to a visit / trial / task / quote / ticket / contract, or dismiss the suggestion (Link a thread to a record).
Noise such as newsletters, notifications, and auto-replies isn't synced. On the Email account (E-posta hesabı) page, admins can use the Organization email rules (Kuruluş e-posta kuralları) card to skip certain domains entirely or to stop creating people from them.
Categories
Every thread is put into a category automatically (v50): Customer correspondence · Quote / price · Orders and shipping · Support / complaint · Invoice and payment · Newsletter / notification · Other (Müşteri yazışması · Teklif / fiyat · Sipariş ve sevkiyat · Destek / şikâyet · Fatura ve ödeme · Bülten / bildirim · Diğer).
- How it's chosen: a keyword in the subject counts strongly, one in the body weakly (the body needs at least two different keywords; signatures, quoted text and e-mail addresses don't count). Threads linked to a quote, order or support ticket go to that category; a newsletter-like message from a bulk sender (noreply…) becomes Newsletter / notification. A company thread that matches nothing is Customer correspondence, a thread without a company Other.
- AI: with the AI module on, threads are classified by keywords at once and by AI a few minutes later (last 120 days, up to 300 threads a day; only the subject and a short excerpt are sent, no addresses or phone numbers). If the AI doesn't answer, the keyword result stays.
- Changing it: click the category chip in the Emails list, in the thread page header or on the deal's Emails tab — pick another category or Classify automatically; Undo after a change. A category set by hand stays when new messages arrive. The thread's owner, the company owner or an admin may change it.
- Filtering: the category strip under search on the Emails page — click to see that category's threads (with counts).
- Settings → Email categories (admin): name, colour, keywords, order (on a tie the higher one wins), on / off; add categories, Reclassify, Back to defaults, Classify with AI switch. Customer correspondence and Other can't be deleted.
Projects
- The Emails → Projects tab shows threads linked to a project (deal), project by project: company, project and stage, number of threads, threads awaiting a reply and the latest threads. The project name opens the deal page's Emails tab. Threads in the customer follow-up container and company-level threads are on the Threads tab.
- The deal page → Emails tab (next to Overview) lists all of the project's threads full-width: category, a short excerpt of the last message, person, date; All · Awaiting reply and category filters, search, Write e-mail.
Privacy
The mailbox owner chooses how it's shared: full (tam), where the team sees message content, or headers only (yalnız üst bilgi), where the team sees subjects and people but the content is hidden. Users who aren't allowed to see the content receive messages with body: null, hidden: true. This rule also applies to the API and MCP.
Thread fields
| Field | Type | Description |
|---|---|---|
id |
integer | Thread ID. |
subject |
string | Subject. |
customer_id, customer |
integer, string | Linked company. |
opp_id, opp, opp_how |
integer, string | Linked project and why it was chosen (chain, compose, single, number, recent, manual…). |
suggested |
boolean | The project is only a suggestion (recent). |
n, last_at, last_dir |
integer, datetime, string | Message count, time of the last message, and its direction (in incoming, out outgoing). |
waiting |
boolean | The last message was incoming — awaiting a reply. |
peer |
string | The last external person in the thread. |
category, category_label, category_color, category_source |
string | Category (v50): key, name, colour, source (rule keywords · ai · user by hand). Change it with Set a thread's category; filter with ?category= on the list. |
The single-record endpoint also returns messages, links, companies, suggestions, linkables, may_edit, and a ready-made reply for responding (recipient, Re: subject, in_reply_to).
Sending
The Send an email endpoint sends the message from the user's own account; the message also lands in the Sent folder and is linked to the thread. Bulk sending and email sequences are available only in the web interface (Email Automation module).