Centilio Relate
at launch Every reply, classified onto the right customer record with the campaign that caused it. An unsubscribe here suppresses them there too.
A reply arriving on the right customer record is the whole point of Pulse, and it is not a connector — Relate is the same company and the same record. What is left is your sending domain, the mailboxes you already reply from, a way in and a way out. Everything on this page is marked at launch or after launch.
Product design preview · Pulse has not shipped. All features, screens and prices are proposals.
Pulse has not shipped. These screens, features and prices are proposals, not an app or beta. Email Outreach is described in the source as its precursor—not the full Pulse product. See the product directory for current stages.
Demand moves the order. If a channel or a connector decides whether you could use Pulse, tell us and it moves up — WhatsApp is near the top of that list already, because the Indian demand for it is larger than the Indian demand for email software.
at launch Every reply, classified onto the right customer record with the campaign that caused it. An unsubscribe here suppresses them there too.
at launch Who may send, who may only draft, who may approve a big send — roles set once and followed here.
at launch A reply becomes a quote, the quote is signed, the signed quote becomes an invoice. Pulse is the first step of that chain.
after launch Signup forms that grow the list honestly, with the source recorded on the day they join.
after launch A landing page to put the form on, and a reply that becomes a meeting.
at launch SPF, DKIM and DMARC on a domain you own, with the DNS records written out and checked. Not a shared blasting pool.
at launch Several sending addresses on one domain for outreach, rotated with per-mailbox caps. Unlimited on Business, at no extra cost.
at launch Connect the mailbox you already reply from, so a sequence stops the moment you answer by hand.
at launch Receipts, resets and confirmations on the same authenticated domain, kept apart from marketing so one cannot poison the other.
after launch For senders with the volume to keep one warm — with a plain warning when your volume is too low to benefit.
at launch Fifty rows first, looked at properly, then the rest. Bad addresses flagged before they cost you a reputation.
at launch Everyone who ever unsubscribed or complained, brought across first. Emailing a past unsubscriber is the worst first send you can make.
at launch Every contact, every campaign, every reply, on every plan including Free, any time.
after launch In India this is the same purchase as email. Planned, and it says so rather than appearing in a screenshot.
after launch Where it is the channel that actually gets read. After launch, priced at cost plus nothing clever.
at launch Contacts, segments, sends and reply events, so the things we have not thought of are still possible.
after launch Through the API at launch; direct connectors after, in the order people ask.
Somebody answers a campaign. Celia classifies the reply — interested, not now, wrong person, unsubscribe — and it appears as a conversation on that customer's record in Relate with the campaign attached. If it was interesting, a deal opens. If it was an unsubscribe, that person is suppressed in both tools at once and cannot be emailed from the CRM either.
None of that is a sync that breaks at 2am. Pulse and Relate are both wave 2 and are being designed against the same record, which is why the connection is a design decision rather than a roadmap item.
The Centilio tools, because they share a record rather than sync to one: Relate for the customer record and the replies, Account for roles, Bill and Sign so a reply can become a quote and an invoice. Outside that: an import, an API, webhooks and an export.
It is not a connector. A reply arrives, Celia classifies it, and it appears as a conversation on the right customer record with the campaign attached. An unsubscribe in Pulse suppresses that person in Relate too, and a customer marked lost in Relate drops out of the sequence here.
After launch, and honestly so. In India WhatsApp is the same purchase as email — the demand is larger than the email demand — and a tool that ignores it is written for an American reader. It matters enough to build properly rather than ship as a link.
Not in the first release. If your business runs on abandoned-cart and product-feed automation, Klaviyo is the right answer and we say so on their comparison page.
On Business, at launch: contacts, segments, sends and reply events, with webhooks. Transactional sending is on the same API and the same authenticated domain, kept apart from marketing so one cannot poison the other.
Through the API at launch; direct connectors after, in the order people ask for them.
The tools Pulse sits between. Check each product’s current stage while Pulse is built.
These proposed connections depend on the participating products launching. No shared-record service is operating in this preview.
Every reply, on the right customer record
The form that grows the list, filed with its source
A reply that becomes a meeting
The article the newsletter links to
The quote the sequence was arguing for
The landing page the form lives on
Wave 2 is the next build after the currently available tools. Leave your name and you will hear before the announcement — and tell us what you actually send, while it is still being designed.