From Buy toLive in 3 StepsWorks as YOUR business — never hello@, never shared.
This is the exact path a customer takes from marketplace card → Stripe → connecting their Twilio + Google → Workflows running from their number, branded as {{tenant.name}}. No hello@, no placeholder, fully tenant isolated.
Trust proof • Technical
ISOLATEDNo hello@ ever
Sender always customer
Tenant vault
Encrypted per business
Isolated runs
No cross-tenant read
Template → Live
is_template false
config_json diff (preview):
- "from": "{{tenant.connected_accounts.twilio.phone_number}}"
+ "from": "+15552478891" // YOUR number
- "brand": "{{tenant.name}}"
+ "brand": "Parkside Plumbing Co."
→ is_template: true → false
BYO model guarantee
Customer connects THEIR Twilio, THEIR Google. Platform never shows hello@.
ConnectedAccount encrypted, tenant isolation enforced in RLS.
Browse 52 live services
Filter by department, tier, provider. Every card is a deployable product, not a template.
Lead Capture Instant
Missed Call Text-Back
Appointment Booker
Review Request Auto
Quote Follow-Up
Smart Intake Qualify
What happens in backend
- 52 services, 6 departments: Sales, Voice, Marketing, Support, Operations, Social
- Each with workflow JSON, config_json with mustache placeholders
- White-labeled: never references hello@ or Relay branding in output
{ "is_template": true, "config": { "message": "Hi {{lead.name}}, {{tenant.name}} here — got your {{service.requested}}" } }{ "is_template": false, "tenant_id": "parkside_plumbing_91x2", "resolved": "Hi Alex, Parkside Plumbing Co. here — got your kitchen remodel" }Operator proof
Workflow
active
Vault
encrypted
Tenant
isolated
White-labeled guarantee
Your customer never sees Relay. Only {{tenant.name}}.
Every workflow ships as a template with mustache variables. On activation we resolve to tenant reality. The SMS sender is customer-owned Twilio, the email domain is theirs when provisioned, the calendar is their Google. Logs live in tenant-isolated tables with RLS, never visible cross-tenant. That is why BYO in 20 seconds really means BYO.
FROM is always YOUR number
Twilio BYO verified, then {{tenant.connected_accounts.twilio.phone_number}} resolves to +1 YOUR.
Brand is always {{tenant.name}}
SMS body, email signature, calendar summary all inject business name at runtime.
Zero hello@ leakage
Platform support email is hidden behind branded from_local_part. Real inbox only for hello@ if provisioned.
Template stored in ServiceCatalog
{
"is_template": true,
"nodes": [
{
"type": "sms",
"config": {
"from": "{{tenant.connected_accounts.twilio.phone_number}}",
"to": "{{lead.phone}}",
"body": "Hi {{lead.first_name}}, {{tenant.name}} here — got your {{inquiry.service}}"
}
},
{
"type": "google_calendar.create",
"config": {
"summary": "Booking — {{lead.name}} — {{tenant.name}}"
}
}
]
}Live after activation • Parkside
{
"is_template": false,
"tenant_id": "parkside_91x2",
"nodes": [
{
"type": "sms",
"config": {
"from": "+15552478891",
"to": "+15558821190",
"body": "Hi Alex, Parkside Plumbing Co. here — got your kitchen remodel"
}
},
{
"type": "google_calendar.create",
"config": {
"summary": "Booking — Alex Carter — Parkside Plumb...",
"for": "owner@parksideplumbing.com"
}
}
],
"vault": "isolated",
"brand_proof": "{{tenant.name}} = Parkside Plumbing Co."
}See it live, then sell it as yours.
This page is the demo the video model could not render. No placeholder images, no stock human shots. Only the actual marketplace, the actual Stripe checkout, the actual BYO vault flow. Works without connecting any account to view.
