Fit the assistant to your website
Use owned content to answer visitor questions with less friction.
7-day free trial
What this feature covers
Why it matters
The practical reason to use it.
Customization is where the assistant becomes ready for a real website launch.
How it works
A step-by-step look at the workflow.
Step 1
Set the domain, branding, launcher, greeting, prompt starter, and disclosure details that define the visitor-facing experience.
Step 2
Configure email delivery, provider keys, and workspace controls to match your review, billing, or agency delivery model.
Step 3
Apply the setup to the assistant, website, client workspace, or product surface that needs its own presentation.
Step 4
Review the launch against real visitor questions and refine visible copy, routing, and control settings as needed.
Core job
The main job this feature handles.
Domain ownership
Use branded domains and SSL-backed setup so the chat experience feels native to your product, site, or client deployment.
Visual identity
Customize logo, colors, launcher treatments, and interface details that shape first impressions before a visitor reads a single answer.
Message framing
Adjust greetings, placeholders, prompt starters, and suggestion copy so the conversation opens in the tone your brand already uses.
Branded email flow
Use custom SMTP and sender identity so notifications and email-based follow-up look like part of your product, not an external service.
Daily use
How teams use it after launch.
Bring your own keys
Use your own OpenAI, Anthropic, Google, or gateway credentials when billing, compliance, or vendor policy needs to stay under your control.
Model strategy
Pair custom provider access with model selection so different assistants can optimize for reasoning depth, speed, cost, or channel constraints.
Environment fit
Adapt the experience for private workspaces, SaaS embeds, agency delivery, or enterprise review without rebuilding the entire assistant setup.
Governed changes
Keep customization changes inside the same workspace permissions and rollout controls your operators already use for assistants and teammates.
Control points
What to keep controlled.
What you get
The changes teams should notice first.
- More trust because the experience feels native to your product and domain
- Cleaner rollout when email, branding, and provider controls live in one platform
- Better cost and compliance ownership with BYOK and deployment-level control
- Less rework when moving from private pilot to public or client-facing launch
The facts do the selling
Plan facts, platform capabilities, and worked examples — every claim here is checkable, not a pitch.
White-label included — never a paid add-on. Copyright removal from $98/mo. Full white-label — custom domain, branded portal, your-domain emails — from $198/mo.
The white-label wedge
Platform fact
Training runs on your sitemap, PDFs, docs, and YouTube transcripts. Answers cite the source pages they came from.
Trained on your content
Platform fact
Five clients at $300/mo on a $198/mo Agency plan is $1,300+ of monthly margin before usage.
A 5-client agency on one flat plan
Worked example
Your questions, answered.
Tap any question about the product, pricing, security, or setup to see a straight answer.
InsertChat
Answers about InsertChat
Hi! Tap any question below and I'll answer it for you.
Customization questions
Can I use my own domain?
Yes. Custom domains are part of the setup so the assistant feels native to the website, client environment, or product surface where visitors ask. The operational question is whether customization makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Is customization only about appearance?
No. It also covers provider keys, email delivery, launcher behavior, greeting copy, and launch decisions that affect how the assistant runs on a real website. The operational question is whether customization makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Can customization stay scoped to one assistant setup?
Yes. The controls are designed so different websites, clients, departments, or assistant launches can keep their own branding, sender details, provider setup, and review boundaries. The operational question is whether customization makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Ready to get started?
Start your 7-day free trial. Review current trial terms.
7-day free trial