1. Concepts
  2. Stub Session

Concepts

Stub Session

How conversations are linked to stubs

Basic Principle

The Stubber platform has integration to many different omni-channel communication platforms.

When a conversation is started on any of these platforms, it needs to be linked to a stub in the Stubber platform.
Stubber keeps track of the conversation and the stub it is linked to with the concept of a stubsession.
A stubsession is simply a link between a conversation and a stub.

Notification Platforms

Each notification platform has a unique way of linking a conversation to a stub. The most advanced usage of a stubsession is in the Whatsapp platform.
The Whatsapp platform requires the careful management of a session to handle the context switching that might happen within a single thread between a user and a number.

You can find more information on how each notification platform sets and expires a stubsession in the respective documentation for that platform.

Key Concepts

Setting a Stubsession

When a new message is sent from a stub the stubsession can easily be linked.
When a message is received from a user, the message needs to be routed to a stub and then a stubsession needs to be initiated (mostly by responding to that message).

Stubsession Expiry

A stubsession can expire after a certain amount of time or explicitly by using a task.
The stubsession can also become obsolete if a new stubsession is set between the same two endpoints.