Create your first website assistant
Sign in to the platform console, open Assistants, set a name, try the playground, then install on your site.
Contenido en inglés
1. Open Assistants
- Go to platform.ismscopilot.com and sign in (or create an account).
- Open Assistants (route
/embed). If you do not see it, hard-refresh.
Emails after signup
New platform accounts receive a short onboarding sequence about API keys, the Assistants embed, credits, and the console. Every email carries an unsubscribe link that stops the sequence immediately.
The signup form also has an optional, unchecked box ("product updates and tips"). Ticking it additionally opts you in to occasional product-update emails; you can withdraw at any time via the unsubscribe link in any email. Leaving it unticked never blocks signup or any product feature.
2. Accept partner terms and create the workspace
On first use you create a partner profile:
- Enter a Company / product name (your practice or product). This is also the default spoken company when visitors ask who the assistant works for.
- Accept the Embed terms, DPA, and subprocessors package linked from the console. Those documents are also on trust.ismscopilot.com.
New workspaces start on the Free tier (see Plans and usage for live allowances).
3. Set the assistant name (recommended)
Open the Assistant name card and set the public bot brand visitors should see in the header (for example your product name). Save, then use the playground.
Details: Assistant name and attribution.
4. Playground
The playground is the first surface:
- Type a compliance question a visitor might ask.
- Confirm a streamed answer appears.
- Ask “what is your name?” and “who are you?” to check brand speech.
- Use this to validate tone and knowledge before putting the widget on a public page.
Playground traffic uses a short-lived preview session minted for the platform origin. It is for you, not for end customers.
5. Install on your website
Click Embed on my website. The install panel expands and scrolls into view (it is not buried under upgrade).
Continue with Install the embed snippet.
6. Optional: EU processing (Growth+)
If you need Advanced Data Protection routing for embed traffic, enable EU processing on Growth or higher. Free and lower paid tiers see Upgrade to enable EU processing, which scrolls to the upgrade section (#embed-upgrade).
See EU processing.
7. Optional: upgrade when free replies run out
Free accounts see upgrade options under Need more replies? (and the upgrade block with id embed-upgrade). Paid tiers use Stripe checkout with reply allowances. See Plans and usage.
Conversations
Visitors get multi-turn Q&A while the widget stays open. There is no visitor-side history sidebar in the widget yet. Partners can review transcripts in the console Conversations inbox where history is enabled on that environment. See Conversations and history.
If the playground fails with a network or CSP error, check that the browser can reach the partner-chat production host listed in the console, and that you are not blocking third-party scripts on the platform origin.