Skip to content
Workflows

Show a contextual invitation on a website page

Offer help where it is relevant without repeatedly interrupting the same visitor.

Where to find itWorkflows → website trigger → invitation action

Before you begin

Open Workflows in the workspace navigation. Decide which event should start the flow and which agents should receive it. Start with an unpublished draft.

Example workspace · Demo data. Follow the path from starting event to decision and action. Select the image to enlarge it.
Workflow canvas with trigger, condition, actions and settings

Example workspace · Demo data. Follow the path from starting event to decision and action. Select the image to enlarge it.

Step by step

  1. 1

    Choose the page event

    Use a supported website event and a page condition. Match the actual public URL structure, including any locale path you intend to include.

  2. 2

    Add relevance and restraint

    Use offered visit, timing, message or history conditions so the invitation fits the visitor’s situation.

  3. 3

    Write specific copy

    Explain the help available on that page. “Need help choosing a frame size?” is more useful than an unrelated generic sales prompt.

  4. 4

    Preview and test

    Check desktop and mobile, timing, dismissal and repeated visits. Verify the invitation does not cover essential website controls.

  5. 5

    Publish to the intended agents

    Save assignments and check the real embedded agent. A flow assigned to another bot ID cannot affect this widget.

Good to know

Visual launcher design stays in Appearance. The decision to show a contextual invitation belongs in Workflows.

Check the result

Test matching, non-matching and missing-data cases. Review the publication, publish the steps and save the intended agent assignments.

Questions & troubleshooting

It appears on every page

Review URL operators and all/any grouping. Test an unrelated page as a required negative case.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.