Developer/IT > Whisbi API > API Reference > Events > One-to-One: Start

One-to-One: Start

Events that trigger before the customer has entered on a One-to-One session

NameDescriptionRequired
otoOpened function The One-to-One sidebar opens Location: Whisbi floatting button
Triggered: Every time the One-to-One sidebar opens regardless from a click on the floating button, an auto open setting or a custom button.
Exceptions: If a customer is already in a session and reloads the landing, this event won’t be triggered again.
Optional
otoPreSessionRequest function The customer has requested a call me now, call me back or scheduled session but the client wants to modify or add some data before the request is made. The client will be able to modify the seed, contentId, callCenters or extra field. Location: Call me now, Call me back or Schedule request.
Triggered: Just before the otoCallBooked, otoCmbRequested, otoSessionRequested events Returns: { seed: '', contentId: '', callCenters: [ '' ], customer: { name: '', phone: '', country: '', email: '', extra: '', dialCode: '', date: '', time: '', formatedDate: '', simplyBookDate: '' } }Callback parameters: { seed: '', contentId: '', callCenters: [], customer: { extra: '' } }
Optional
otoSessionRequested function The customer has requested a call me now session Location: Call me now request
Triggered: Just before showing the hold screen to be attended.
Exeptions: If a smart landing is displayed, this event is not triggered. If a customer clicks on the “Continue on hold” button from the smart landing it is not sent until an agent is available. If we reload the landing while we are waiting, it won’t be triggered again. Returns: lead, name, phone, email, extra, kpiGuid
Optional
otoInboundClicked function The customer has clicked the mobile inbound option Location: Inbound screen or inbound chatbot node on mobile
Triggered: It is triggered just before the mobile dial pad is opened or in case of having GDPR, it will be triggered after it is accepted. Returns: phone
Optional
otoInboundToWhisbiLoaded function The customer sees the Inbound number on desktop Location: Inbound screen or inbound chatbot node on desktop Returns: formatted_phone, phone Optional
otoCallBooked function The customer just booked a One-to-One call for an specific date and time Location: Schedule
Triggered: A schedule call has been booked successfully. Returns: leadGuid, sessionGuid, kpiGuid, country, extra, name, phone, scheduledDate, scheduledDateObj
Optional
otoCmbRequested function The customer has requested a One-to-One Call Me Back Location: Call me back request Returns: lead, name, phone, email, extra Optional
otoPinCodeGenerated function The Pin to Whisbi code has been generated Triggered: Widget generates an alpha numeric pin in the landing regardless of whether it is shown or not. Also shown within the Tap to Call and Transfer Call screens. When a customer ends a session the PIN is refreshed and the event is triggered again. Returns: pinCode Optional
otoInvalidPhone function The Customer is trying to send a form filled with an invalid phone number Triggered: Just after clicking the submit button of the form containing the phone field. Returns: session, cookie, name, phone, email, extra, kpiGuid Optional
otoCallError function The Customer or the Agent doesn’t pick up the phone Triggered: Every time a call is made to the Customer or the Agent before a session, and the call is not picked up. Returns: session, cookie, name, phone, email, extra, kpiGuid Optional
otoNoAgentsAvailable function There are no agents available when a session request is made Triggered: Just after the submit button of the Connect form is clicked. Returns: session, cookie, name, phone, email, extra, kpiGuid Optional