Beyond colors and sizes, the chat widget has several content surfaces you can configure — the welcome message, the chat placeholder, the start-chat button, the predefined inquiries on the home view, and how the assistant ends a conversation. This article maps every content field and tells you what to write in it.
In this article
Where widget content is configured
The four message fields
Predefined inquiries
Pre-chat survey content
Auto-end conversation content
Localizing your widget content
A short copy guide
Where widget content is configured
Two places, depending on what you're editing:
Publish → Widgets → Bubble widget → Manage → Content — the assistant's default English content (chat welcome, placeholder, start-chat button, predefined inquiries) plus customer-satisfaction prompts.
Settings → Language → {language} — translations of the same content for every locale your widget supports.
If your store only sells in English, the first surface is enough. If you sell in multiple languages, you'll also use Settings → Language to translate the content for each.
The four message fields
Inside the Content block of the Bubble widget modal:
Field | What shoppers see | Suggested length |
Chat welcome | The first assistant message when the chat opens. | 1 sentence |
Placeholder | Text inside the chat input field before the shopper types. | 2–4 words |
Start chat button | Label of the button that opens the chat from the widget's home view. | 1–3 words |
Predefined inquiries | Suggested first messages shown as chips on the home view. | 4–6 words each |
💡 Tip: Treat the Chat welcome like a storefront greeter. "Hi! How can I help you today?" is fine; "Welcome — ask me anything about our products, returns, or shipping." is better. Specific beats generic.
Predefined inquiries
The home view of the widget shows a stack of suggested questions. Shoppers click a chip and the conversation starts with that message already typed.
Add one chip per question.
Reorder by removing and re-adding (top of the list is the most prominent).
Aim for 3–6 chips total. More dilutes attention.
Good chip examples:
Track my order
What's your return policy?
Help me find a gift
Do you ship to my country?
Compare two products
Bad chip examples (too vague / too long):
Ask anything
I need help with my recent purchase that hasn't arrived yet
Pre-chat survey content
If you've enabled the pre-chat survey (name + email modal before the chat starts), its copy lives under Settings → Language → {language} → Pre-chat survey:
Survey message — the welcome text shown above the inputs.
Name placeholder / Email placeholder — placeholder text for the input fields.
Start chat button — the label of the primary button.
Skip button — the label of the secondary "skip" button.
See Setting up Predefined Inquiries & Pre-chat Surveys for when to actually enable the survey.
Auto-end conversation content
After a conversation is resolved, Convi can ask the shopper for a thumbs-up / thumbs-down rating. The copy for that flow lives under Settings → Language → {language} → Auto-end conversation:
Title — the heading on the rating prompt.
Negative reason — the label on the free-text follow-up after a thumbs-down.
Negative placeholder — placeholder text in that free-text field.
Negative button — the label on the submit button.
After submission — the toast/message shown after the shopper submits feedback.
To turn the satisfaction prompt on or off itself, use Publish → Widgets → Bubble → Customer satisfaction feedback — "Collect customer satisfaction feedback through a like or dislike rating after resolving the user's inquiry."
Localizing your widget content
Every content field above can be translated per locale. Open Settings → Language, pick a language, and you'll see sub-screens for:
Welcome messages — chat welcome + placeholder + start-chat button.
Predefined inquiries — the chip list, per locale.
Pre-chat survey — survey message + placeholders + button labels.
Auto-end conversation — the satisfaction flow.
FAQ widget, Ask AI button, Contact Us embed — the same per-surface content for the other widgets.
Translations save independently. If you ship Convi in 5 languages, you'll have 5 versions of each field.
A short copy guide
Field-agnostic rules that hold up across stores:
Speak in your brand voice, not Convi's. Generic copy reads as generic — match the tone the rest of your store uses.
Imperative beats descriptive. "Find a gift" beats "Get help finding a gift."
Don't promise what you can't deliver. "Get an answer in seconds" is fine; "Get the right product recommendation in seconds" is a promise that won't always hold.
Test with a real question. Open the widget on your storefront, click each chip, and confirm the resulting conversation goes somewhere useful.