Before we build, we need to understand your stack.
This takes about 10 minutes. Your answers give us everything we need to configure the inbox intelligence system accurately from day one — no back-and-forth, no delays.
// 01 of 04
Credentials & Access
We need access to your core platforms to connect the system. You won't need to share passwords — just confirm what's available and how you'd like to grant access.
🔒
Secure credential sharing: We recommend using a password manager share (1Password, Bitwarden) or a one-time link service like onetimesecret.com. Never send credentials in plain text over email.
We'll be migrating this to a self-hosted Railway VPS as part of the build.
We need to confirm API + webhook access is available on your current plan before building.
Approx. total across all clients
API access required
Which channel should positive reply alerts route to? Use an existing channel or name a new one.
List names or roles — just Anthony, or the full team?
// 02 of 04
Inbox Intelligence
This is the most important section. The accuracy of the AI classification system depends entirely on how well we understand what a "positive reply" means to you.
⚡
Why this matters: The Claude classification prompt is trained on exactly what you tell us here. Vague inputs = misclassified replies. Specific inputs = a system that routes the right leads instantly, every time.
Who sees it first? How fast? What do they do with it? Describe the exact manual process being replaced.
0 chars
Give us exact phrases, intent signals, and examples. The more specific, the better the classifier performs.
0 chars
Auto-replies, OOO messages, unsubscribes, negative responses — what gets suppressed?
Any edge cases or specific phrases that should never trigger an alert.
// 03 of 04
Drafted Responses
Every Slack alert will include a pre-drafted response. This section tells us exactly what that draft should look like so you can approve and send in one click.
This becomes the tone and style template for all Claude-generated drafts. The more examples the better.
0 chars
What action are you driving toward in every reply?
If you're driving to a booking CTA, paste your link here so it auto-embeds in every draft.
If a VA or inbox manager is still active during the transition, we need to know to prevent double-firing alerts.
// 04 of 04
Final Confirms
Last section. Infrastructure decisions and timeline coordination — this is where we lock in the build sequence.
The build includes migrating your n8n instance to a self-hosted Railway VPS (~$5/mo). Frank manages this under the retainer.
Phase 1 does NOT include ScaledMail auto-provisioning — that's a Phase 4 expansion. Confirm you're aligned on this scope boundary.
Phase 1 goes live within 10 business days of build start. When are you generally available for a 30-min test/handoff session?
✓
We're good to go.
Your onboarding info has been submitted. Frank will review everything and be in touch within 24 hours to confirm API access and lock in the build start date.