The AI drafts. You press send.
SocialPilotix plans and writes your onboarding, activation and win-back email from the data already in your Postgres database. Every message waits in a queue until a person approves it. The agent cannot send, approve or delete anything. That is enforced by the database, not by a prompt.
One fixed pipeline. One step belongs to a person.
The agent does not improvise its own workflow. It runs the same seven steps every week, and the sixth is never automated.
- SegmentPicks who is due a message, from consented users only.
- PlanReads last week’s results and decides what to try.
- DraftWrites each message in your brand voice, from your product facts.
- CheckRules block personal data, unknown links and risky claims.
- QueueDrafts land in a review queue. Nothing has left yet.
- ApproveYou read each draft and approve or reject it.
- SendA separate worker delivers approved mail and records the result.
Built for the failure cases, not the demo.
An AI that can email your customers is a liability until the limits are real. These are the limits.
The agent has no send button
It runs under a database role that can read pseudonymised segments and add drafts. Sending, approving and erasing are separate roles it does not hold.
The model never sees a name or address
Users are referenced by salted hashes. Drafts are scanned for personal data by value before they can be queued.
Unsubscribe always works
Every email carries a signed one-click unsubscribe link. Bounces and complaints suppress the address automatically.
One switch stops everything
A kill switch halts drafting and delivery. Sending starts disabled, and first runs go to an allowlist of your own inboxes.
Every decision is logged
What was segmented, planned, drafted, blocked, approved and sent is written to an append-only audit log you can query.
Access and erasure are commands
Exporting or erasing one person’s data is a single documented command, so a GDPR request takes minutes.
For small teams that sell to businesses, consumers, or both.
One queue, two kinds of customer, different rules for each.
Trials that go quiet
Spot accounts that signed up and stalled, and draft the nudge that names the step they missed. You approve it before anyone at that company sees it.
Customers who drift away
Win-back and activation messages, only to people who opted in, with a cap on how often any one person hears from you, with the unsubscribe link first-class.
What it is, plainly.
- Email first. Lifecycle email is the only channel today. Others come after this one is proven.
- Your database. It works from a Postgres database you control, not a copy in someone else’s cloud.
- EU by default. Hosted in the EU, operated by a Swedish company, with the GDPR paperwork written alongside the code.
- Not live yet. It is in private build. The waitlist gets one email, when it opens.