Install the messenger

Summer's messenger brings website conversations into your support workflow. Start with public support and clinician links. Connect verified identity when you want patient-specific destinations.

Choose your setup#

You do not need to share clinical-system API keys just to link someone to their own care page.

Create an installation#

1. Sign in to Summer and select your company.
2. Open Settings → Integrations → Summer Messenger → Set up messenger.
3. Create an installation. Enter your support name and exact website origins, such as https://www.example.com. Add each origin separately; paths and wildcards are not accepted.
4. Add your clinician-chat destination, sign-in destination and public care/catalog page. These destinations are optional; Summer will not invent a missing URL.
5. Enable Allow visitors without an account for a basic embed. Enable customer messaging when your installation is ready to test.

For a company-hosted installation, Open website conversations opens its own inbox in Summer. Staff can read original messages and attachments and send a reply; a staff reply pauses the assistant. Rebody’s built-in installation continues to use its existing support cases.

The installation belongs to the selected company and environment. Keep staging and production separate.

Add the snippet#

Replace YOUR_INSTALLATION_UUID with your installation ID. See Find your installation ID. Put the configuration before the asynchronous loader.

<script>
window.summerMessengerConfig = {
  installationId: "YOUR_INSTALLATION_UUID"
};
</script>
<script src="https://gosummer.ai/messenger/v1/loader.js" async></script>

The installation ID is public. The signing key is private and does not belong in this snippet.

Find your installation ID#

Each installation has its own ID, a UUID such as 4f6c1b2e-8d3a-4c7f-9e15-2a6b0d9c3e71. Staging and production installations have different IDs.

• In Summer: sign in and select your company. Open Settings → Integrations → Summer Messenger → Set up messenger, then choose the installation. Its ID shows under the picker with a Copy button. The Basic embed and Embed and identity integration snippets on that page already contain it.
• When you save a new installation: the receipt shows the ID.
• From the CLI: after summer login, summer messenger list --json -c COMPANY_ID -e staging lists each installation with its id.
• From a setup file: summer setup apply reports each installation's ID in the installation field of its result. See Set up from a project.

Only company owners and administrators can open the messenger settings. If you cannot open them, ask one of them for the ID.

If your site uses Content Security Policy, allow the Summer host for the script, frame and connection requests the embed uses. Apply your application's normal nonce or hash to the inline configuration if your policy requires one; allowing the external loader alone does not allow that inline script. Test the embed with your actual production policy.

Connect your accounts later#

Add getIdentityAssertion when your backend can verify the current login. Follow Connect signed-in accounts. A visitor's name, email or date of birth is not proof of account ownership.

Test before rollout#

Use your staging installation and test accounts. Verify that the widget opens, messages arrive, configured links reach the right pages, and signed-out visitors see no account details. See the testing checklist.

Messenger enablement, routine assistant replies and deeper operational actions have separate controls. Enabling the widget does not activate all of them. Your Summer deployment must have the messaging backend configured; contact your Summer administrator if setup reports that the backend is unavailable.