01
The appearance matches your brand
Color, placement, and customer-facing copy are previewed together before you save.
Match your support experience to the product around it.
Website chat that belongs on your site
Choose the appearance, preview the customer view, and add one install snippet when it feels right.
Start with 100 creditsOne-time $1 activation · 100 credits included · No automatic subscription
How it works
Design the customer view before you install it.
Appearance, behavior, and deployment stay in one workflow so the saved configuration matches what visitors see.
- 1
01 · Match
Choose the look that fits your site
Set the color and placement while the live preview updates beside the controls.
Appearance
EditingColor
Brand green
Position
Bottom right
Preview
Updated live
- 2
02 · Preview
Read the chat at customer scale
Check the header, messages, prompts, and composer in the same proportions visitors will use.
Customer view
ReadyOpening message
Visible
Suggested prompts
Readable
Composer
Available
- 3
03 · Install
Add one production snippet
Copy the saved install code into your site and keep later appearance changes inside Communicate.
Install
ProductionSnippet
Copied
Placement
Saved
Agent
Connected
The support feels like your product. The setup stays inside Communicate.
What changes
A support surface that feels native to your website.
Customers should notice the help, not the vendor that rendered it.
02
The install stays small
One snippet loads the Widget while later content and behavior changes remain in your workspace.
03
Page styles stay separated
The Widget surface is isolated so its controls do not inherit accidental styles from the host page.
Designed for the edge cases
Preview the details that make an embed feel trustworthy.
The customer experience is easier to ship when the exact surface stays visible during setup.
Live appearance preview
Color and placement changes update the customer view beside the controls.
You stop dealing with: saving blindly and refreshing a staging site after every adjustment.
Opening state and prompts
Review the first message, suggested questions, and composer before the Widget reaches visitors.
You stop dealing with: discovering cramped or unclear copy only after launch.
Shared Agent configuration
The Widget uses the same Agent, knowledge, rules, and handoff model as the rest of Communicate.
You stop dealing with: maintaining a second bot just for the website.
Single install snippet
Install once, then manage saved appearance and behavior from the workspace.
You stop dealing with: asking engineering to redeploy for every support copy change.
What you save is what customers see
Keep the customer view beside the configuration.
Small visual decisions become safer when the preview is immediate and readable.
Appearance
Color changes reflect in the chat
The header and visitor message update with the selected theme.
Content
Opening copy stays visible
Review the first interaction before the customer opens it.
Install
Saved settings match deployment
The production snippet uses the configuration already approved in the preview.
Choose how support enters the page
A configurable Widget instead of a separate mini website.
Compare the work required to keep the embedded experience consistent.
Brand preview
CommunicateLive beside controls
Hosted chat pageVendor template
Custom embedYou build it
Site integration
CommunicateOne snippet
Hosted chat pageCustomer leaves site
Custom embedCustom code
Style isolation
CommunicateEmbedded surface
Hosted chat pageSeparate page
Custom embedYou maintain CSS
Agent and Inbox
CommunicateShared system
Hosted chat pageVendor dependent
Custom embedYou build it
Questions before you start
Questions before adding the Widget.
What your team controls and what visitors see.
Make website chat feel like part of your product.
Choose the appearance, read the customer view, and install only when the experience feels right.
Start with 100 creditsOne-time $1 activation · Grounded answers · Human takeover · Cancel anytime