Onboarding

Onboarding usually takes only a few steps depending on the channels you want to configure for Fallback.

Onboarding can be done using the following steps:

1. Go through the Know Your Customer (KYC) process. For more information, see the Completing the Know Your Customer (KYC) page.
2. Activate the following channels:
   1. WhatsApp:
      1. Create a Business Manager ID. For more information, see the WhatsApp Activation page.
      2. Get an approved WhatsApp number. For more information, see the WhatsApp Registration page. Fallback can only be used with WhatsApp V1 numbers.
      3. Get an approved template. For more information, see the Template Creation page.
   2. SMS:
      1. Get a Sender ID to send SMS. For more information, see the Create a Sender ID page.
      2. Create an SMS template. For more information, see the Create an SMS Template page.
3. Reach out to the Support team to enable the Fallback feature for your Kaleyra platform account.

Lifecycle of a Fallback

The lifecycle of a Fallback comprises the following stages:

• Create a Fallback - Once you meet all the criteria of Onboarding, you can start creating a Fallback through the UI-based wizard.
• Save as Draft - You can save the Fallback as a draft and publish it at a later time.
• Publish a Fallback - Once you publish the Fallback, a Workflow ID is generated. You can send message using the published Fallback through API using its Workflow ID.
• Edit a Fallback - You can edit Fallback flows both in Draft and Published status.
• Unpublish a Fallback - You can unpublish a published Fallback. If you unpublish a Fallback, the workflow will transition to the Draft state. Moving a flow to Draft does not impact running executions against that workflow; those existing executions will continue running to completion. Once moved to draft, the same Workflow ID will still be associated with the workflow, but you will no longer be able to invoke it.
• Delete a Fallback - You can delete a Fallback with a Draft or Published status. Deleting a published flow does not impact running executions against that workflow; those existing executions will continue running to completion. Once a workflow is deleted, you will no longer be able to invoke it.