Product

Six capabilities over one contact record, with two things running underneath all of them: a gate that decides whether an outbound message is allowed to leave, and a ledger that knows what every message cost.

The shape

A contact is one record. Every conversation, appointment, pipeline position, consent decision and message attached to that person hangs off it, in one place, in every capability below. There is no separate "marketing contact" and "support contact" that drift apart, because there is one table and the whole product reads it.

Above that record sits the automation engine. It reacts to what happens - a form filled, an appointment missed, a stage changed, a period of silence - and it runs the sequence your industry already needed rather than one you had to invent.

In front of every outbound message sits the gate. It is not a setting you turn on. It runs on every send, and when it cannot establish that a send is permitted it refuses.

Every capability

• Contacts and pipelines
• Unified inbox
• Automation builder
• Booking and calendars
• Campaigns
• Reporting and analytics
• Compliance and A2P
• White-label

What it is deliberately not

• Not a blank canvas. The industry packs ship stages, fields and sequences already named, because a blank automation builder is a project, not a product.
• Not a compliance service. The tooling helps you meet your obligations; it does not assume them. The Terms say so in the same words this site does.
• Not a reseller skin. The database, the API and the migrations are ours, which is what makes the isolation story checkable rather than repeated.