Configuration
The session timeout and custom actions, under Integrations → Live View.
Live View has two organisation-wide settings, found on the Live View tab of your organisation's Integrations page (Integrations > Live View). Any member can see them; changing them needs the integrations.update permission. Every change saves as you make it.
Session timeout
Agents that crash or lose their connection can leave sessions open forever. The session timeout closes a session automatically once it has logged no activity for the chosen period:
- End sessions after 5 minutes of inactivity
- End sessions after 15 minutes of inactivity
- End sessions after 30 minutes of inactivity (default)
- End sessions after 1 hour of inactivity
- End sessions after 4 hours of inactivity
A sweep runs every minute, so a session is closed within a minute of crossing the threshold. When it is, the session's end time is set to its last activity, not the moment the sweep ran - so idle time doesn't count towards your monitored hours, and your agent receives a session.ended webhook with reason: "timeout".
Pick a value that fits how your agents behave. An agent that legitimately thinks for ten minutes between messages needs a longer timeout than a chat agent that answers in seconds; the Quiet status (two minutes) is a hint that a session has gone silent, while the timeout is the point at which Vigilator gives up on it.
Custom actions
Custom actions are buttons shown beside every session's transcript. Pressing one delivers a session.action webhook event to your endpoints, so your agent side can react - pause, hand off, dump state, or anything else you can wire up. Vigilator only carries the signal; the behaviour is yours to implement.
Each action has:
- A name (up to 50 characters) - this is what watchers see on the button and what your agent receives in the event's
actionfield, so treat renaming as a change to your integration's contract. - A colour for the button - zinc, red, orange, amber, lime, sky, violet or pink - so that, say, a destructive abort stands out in red from a harmless dump state.
Press Add action to add one (up to 20), and the × beside an action to remove it. Actions fire with a single click and no confirmation, so keep the names unambiguous. Watchers need the liveView.trigger permission to see the buttons - see acting on a session.
Handling actions on the agent side
Subscribe an endpoint to the session.action event, verify the signature, and switch on data.action. The payload also carries the session's id, your externalId and who pressed the button (triggeredBy) - see the webhooks reference for the full shape.