RECORD EMAIL
CRM email tracking and templates
ranked by the replies they earn
Connect Gmail or Outlook and every thread lands on the record it belongs to, whatever object that is. The composer handles attachments, click tracking, scheduled sends, and per-account signatures. Templates and "/" snippets rank by real reply rates, a send guard blocks unresolved variables, and a sequence stops the moment a contact replies.
Two-way sync
Read and reply where the deal actually lives.
Connect Gmail or Outlook and mail flows both ways: what you send from Ishara lands in your provider's sent mail, and what arrives threads onto the records it belongs to. Matching runs across every object, not just contacts, so a thread shows up on the person, the company, and the deal it concerns. Open the record, read the conversation, reply in place.
- Gmail and Outlook, both directions, no BCC address to remember
- All-object matching: threads attach to any record type, including custom objects
- The composer does real work: attachments, click tracking, scheduled sends, and per-account signatures
Accounts and controls
One settings screen, honest controls.
Each connected mailbox shows its sync state and carries its own signature, so the mail you send from the sales alias and the mail you send from your own address both sign correctly. A blocked-senders list keeps the addresses you never want in the CRM out of it entirely: no thread, no record, no noise.
- Per-account signatures, set once and applied on every send from that account
- Blocked senders stay out of sync and matching altogether
- Scheduled sends leave at the time you pick, not the moment you hit the button
Templates and "/" snippets, ranked by real reply rates
Most CRM email templates rot in a folder sorted by creation date. Ishara's picker sorts by the reply rate each template actually earns from your own sends, so the message that gets answers rises to the top and the one that stopped working sinks. Typing "/" in the composer opens the same picker for snippets: short reusable blocks with typeahead, dropped inline without leaving the keyboard.
Variables make templates safe to reuse. Every variable can declare its own fallback with {{variable|fallback}}, and the send guard enforces it.
How the send guard reads a template. A follow-up opens with {{first_name|there}}, quick question about {{deal_name}}. The first variable declares a fallback, so a contact with no first name gets "there" and the mail goes out. The second declares none, so if the deal name is empty the send blocks and names the missing variable, instead of delivering "quick question about " to a real prospect.
That is the difference between CRM email tracking and templates as a checkbox and as a system: the picker tells you what to send, and the guard makes sure it is safe to send it.
Sequences
Sequences that respect the reply.
Multi-step follow-up with the same guard on every send, and a hard stop the moment the contact answers.
Write the steps
Each step is a template on a schedule. The same variables, fallbacks, and signatures apply as in a one-off send.
Every send passes the guard
Unresolved variables block the step, and suppression is checked before every message leaves. No exceptions for step three.
A reply ends it
The moment a contact replies, the sequence pulls them out. Nobody gets a chirpy "bumping this to the top of your inbox" after they already answered.
Engagement analytics
Numbers you can act on next Tuesday.
Not a vanity dashboard: four views that each answer one operational question.
Send-time heatmap
When do your contacts actually reply? The heatmap shows reply performance by day and hour, so scheduled sends can land at the times that work.
A/B panel
Run two variants of a template against each other and let the reply rate settle the argument, instead of the loudest opinion in the room.
Decay alerts
A template that won for months can quietly stop working. Decay alerts flag a former winner whose reply rate is slipping before it burns a quarter.
Leaderboard
Which templates, and which senders, are getting answered. Useful for coaching, and for retiring the message everyone assumed was fine.
Consent by reason, not by blast radius
CRM email tracking has a reputation problem, mostly earned. Ishara's rails are built so the tracking is something you can defend: links run through branded tracking on your own domain, and marketing sends carry a one-click unsubscribe.
Suppression is scoped by reason. When a contact opts out of marketing, marketing stops, and that is all that stops: a transactional message, like a document sent for signature or an account invite, still delivers. An opt-out list that silently swallows transactional mail is a compliance feature that creates its own incident; scoping by reason is how you honour the opt-out without breaking the business around it.
Everything the thread produces, the sends, the clicks, the replies, lands on the record timeline next to the rest of the deal's history, because email is one stream of the record, not a separate product. See the object CRM for how records are built, or automations for what a reply can trigger. The fastest way to judge it is to connect a mailbox in the app and send yourself a templated mail with the guard on.
Frequently asked questions
Which email providers does Ishara sync?
Gmail and Outlook, two-way. Mail you send from Ishara lands in your provider's sent folder, and incoming mail threads onto matching records automatically. Matching runs across every object, so a thread attaches to the person, the company, and the deal it concerns, including custom objects, not just a contact card.
How does the email tracking work?
Click tracking runs through branded tracking on your own domain, and marketing sends carry a one-click unsubscribe. Suppression is scoped by reason: a marketing opt-out stops marketing mail and nothing else, so a transactional message like a signature request or an invite still delivers. There is also a blocked-senders list that keeps named addresses out of sync and matching entirely.
What stops a template going out with a blank variable?
The send guard. Every variable can declare a fallback with {{variable|fallback}}; a variable that resolves to nothing and has no fallback blocks the send and names the missing field. Sequences pass the same guard on every step, so a broken merge field cannot ship at step three either.
Do sequences keep sending after someone replies?
No. A reply pulls the contact out of the sequence immediately, so no follow-up lands after the conversation has already started. Every sequence step also passes the send guard and the per-reason suppression check before it leaves.
Stop working the market blind.
The investors, the tenders, and the signals are in Ishara from day one. You bring the deals.
Free to start · 32,822 investors on day one · Qatar tenders live, more markets on the way