Prospects who fit your business, contacted every week, every send on the record.
The outbound engine sources businesses to your target profile every week, finds a deliverable address, writes a short opener for each and holds it in a review-first queue. A person releases the batch, or the queue releases on the schedule set for the engagement, and every send is logged with the draft, the mailbox and the time.
What lands in the queue each week?
A short list of businesses that fit your target profile, each with who they are, the signal that made them worth an email, the drafted opener and its status. The list is built every week from a business contact database, filtered to the titles, industries and company sizes set with you, and it arrives on the schedule whether anyone is at a desk. Week two of setup produces the first list for your review.
Suppression runs before a word is drafted. Existing and past customers on the payment record, the do-not-contact list and every address that bounced or said no are matched by exact email, company domain and company name, and removed. The same address is never emailed twice inside 30 days, even when one person matches two segments.
Enrichment then looks for a deliverable address. Only an address that comes back verified or likely to engage passes; a weaker one is never guessed at, and that prospect is routed to a contact-form path instead. A buying signal gates the draft: a company already running paid ads, or one that recently raised money, gets an opener, and one with no signal is skipped that week.
Every draft lands in the review-first queue with its status. Prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged. Releases are paced: 8 seconds between sends and a cap per mailbox per day, 30 by default, so a warmed domain stays warm.
What happens when someone replies?
It is read, classified and put in front of a person. Every reply is matched to the send it answers: an engine-sent thread correlates by the recipient's address, so a missing thread id never loses a reply. The classifier reads the newest message from the prospect's side, not the newest message on the thread, because the newest message on a thread is often our own.
Each class has one fixed handling. A positive reply is raised to your team the same day with the thread and a suggested next step. A reply of no, not interested, unsubscribe or stop ends the sequence, suppresses the address and adds it to the do-not-contact list; nothing follows. A bounce, or a note that the person has left, retires the address and a person decides whether to source the replacement contact. An out-of-office leaves the sequence untouched, because the person is away, not gone. A sender-verification wall holding the message is surfaced for a person to pass, and nothing is paused behind it.
Two things run on a clock so nothing is missed. A sweep every ten minutes re-reads recent mail on the sending mailboxes, read or unread, so a reply someone opened on a phone is still caught and classified. A digest at 8:05am ET lists every positive reply from the last 24 hours and flags any reply on a thread the engine started that was not recorded, so a miss is visible within a day.
No reply is answered by the engine. A real person writing back is a prompt for a person. A prospect who does not reply gets, by default, up to two shorter follow-ups in the same thread, three days apart, each from a different angle. A reply stops them. A thread older than 30 days is left alone, because reopening a cold thread reads worse than silence.
Who decides who gets contacted?
You do, through the target profile. It is set with you during setup: the titles, the industries and the company sizes you want to reach. The Settings view shows the current profile as three lines, titles, industries and company size, beside a cadence card with the outbound rate, so what the engine is aiming at is never a guess.
Change it from the screen. Add a segment from the target accounts card and the request lands with the team, logged, and the next weekly run includes it. Remove one and it stops. Nothing on the screen writes to the engine directly from the browser; every change is a logged request, which is what keeps the record complete.
Named accounts get their own path. Hand us the businesses you specifically want, and each is researched individually, opened with something true and specific about them, and always reviewed by a person before it leaves. They never enter the weekly volume run.
Will it sound like me?
It sounds like the brief you set. Every opener is written to a fixed brief: a few sentences, addressed to a named person at a named company, founder to founder, sharp, specific and warm. No 'hope this finds you well', no fluff, no emojis, no em dashes. It leads with something true about them, says in one line what you do, and makes one low-friction ask. It carries no link; the ask is a reply.
The rules are enforced in code, not left to the model. A deterministic guard rewrites any em dash the model adds anyway. Every email is signed by the person whose mailbox it leaves from, and it ends with a footer that names the sender and offers a one-word exit: reply no and no follow-up goes out. That footer is the promise the opt-out handling keeps.
Openers are short on purpose: one idea, one ask. Follow-ups are shorter still and take a different angle each time, so the second note does not read like the first one sent twice.
Change the voice from the Settings view. Edit the brand voice card and the request lands with the team, logged, and every future draft follows it.
How do I know what was sent to whom?
Open the record. Every send is logged with the prospect, the company, the draft that went, the subject, the mailbox it left from and the moment it left. The time is stamped when the email actually goes out, not when the draft was written, so a draft that waited five days in the queue shows the day it shipped. Every reply is logged with its classification, and a reply stops the follow-ups on that thread.
The stat row at the top of the view shows sourced this week, sequenced, replied, positive and meetings, and each opens. The view refreshes when you open it: the page loads last night's snapshot first, fetches the live payload from a cache instantly, and runs a pull in the background when the snapshot is older than five minutes. Sends, replies and suppressions are live records; sourcing moves weekly.
Know what runs on a schedule and what stays with a person. Sourcing, suppression, enrichment, drafting, follow-ups and classification run on their own. Releasing the queue is set per engagement: a person releases it with one click, or it releases on the schedule set for the engagement. A named account is always reviewed by a person. A reply from a real person is always answered by a person.
Know the ceiling. The engine reads replies on its own threads; it does not read your inbox or your calendar. A not-interested or bounced address is suppressed permanently. Nothing leaves from a mailbox that was not set up for the engagement, and a paused sequence sends nothing, even from a queue that is already full.
What should I check in the demo?
Open the Outbound view on demo.trulata.com. There is no form. The company is fictional and every number is illustrative, but it is the same engine code every client runs.
Look at four things. First, the stat row: sourced this week, sequenced, replied, positive, meetings. Second, one queue row opened: the signal that earned the email, the fit score, the draft marked ready and its awaiting-approval status. Third, the replies card: each reply carries its classification and a suggested action. Fourth, the Settings view: the target accounts card with titles, industries and company size, beside the cadence card with the outbound rate.
Those four are what your own screen shows once the first list is built in week two of setup, with your profile's counts in place of the placeholders.
What the outbound engine reads and writes.
| What | Where it comes from | How fresh |
|---|---|---|
| Prospects | A business contact database, filtered to your target profile | Weekly |
| Suppression | Payment record, do-not-contact list, bounced and not-interested addresses | Before every run; permanent |
| Enrichment | Verified or likely-to-engage address; contact-form path where none | At sourcing |
| Drafts | Written per prospect to the brief set with you, dash guard applied | At sourcing, held in the queue |
| Sends | From the review-first queue, by a person or on the engagement's schedule | Live, logged with draft, mailbox and time |
| Follow-ups | Same thread, up to two, three days apart, stopped by a reply | Daily check |
| Replies | Matched to the send, classified, raised to a person | Ten-minute sweep; 8:05am ET digest |
Prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged.
Questions, answered.
Does it send email on its own?
It can, per engagement. Prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged with the draft, the mailbox and the time.
How are prospects chosen?
By your target profile: the titles, industries and company sizes set with you. A weekly run sources businesses that match, removes anyone suppressed, and drafts only where a deliverable address and a buying signal exist. Change the profile from the Settings view and the next run follows.
What happens to replies?
Each is classified and put in front of a person with a suggested next step. A positive reply is raised to your team the same day. An opt-out ends the sequence and suppresses the address. The engine answers no reply itself.
Will it email someone who said no?
No. A reply of no, not interested, unsubscribe or stop suppresses the address permanently and adds it to the do-not-contact list, and no address is emailed twice inside 30 days in any case.
Can I write the openers myself?
The engine writes them to the brief you set. Change the voice from the Settings view and every future draft follows it. Named accounts you hand-pick get an opener researched and written individually and reviewed by a person before it leaves.
How many emails go out a day?
The cap is set per engagement, 30 a mailbox a day by default, paced 8 seconds apart, and a run only prepares what the busiest mailbox can still take that day. Volume never outruns the sending domain.
Do you need access to my inbox?
No. The engine reads replies on the threads it sent. The dashboard never reads your inbox or your calendar.
Which tier includes outbound?
Command. The full list of what each tier includes is on the pricing page.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.