Termivia video tutorials

Open Templates from the left navigation. This library separates reusable message content from the customers who will receive it. We will prepare an event invitation as a new draft, using fictional example values.

Choose Create template, give it a recognizable name, and select English. A clear name makes the message easier to find later when preparing a campaign or configuring a Customer Flow. Create draft opens the editor.

The editor shows the language and category near the top. Our invitation uses English and the Marketing category. Choose the category that describes your actual message, and check the language before adding the final wording.

Write a short, clear invitation. In this example, first name, event name and event date are placeholders inside double braces. They mark the parts that should change for each recipient or campaign.

Termivia lists the detected variables below the message. Keep each name consistent with your customer data. For example, first name must receive a name, while event date must receive the date you want the customer to see.

The editor requests an example for each variable before submission. Use representative fictional values: Alex, Community Open Day, and 15 November. These examples make the intended message clear without exposing real customer information.

The optional footer is a good place for a concise instruction. Here we add Reply STOP to opt out. An opt-out instruction does not replace marketing consent: only prepare marketing messages for customers with the appropriate permission.

Review the message in the WhatsApp preview. Check the sentence, spacing and footer together. The preview is illustrative and does not send a message. Confirm that your variable names and sample wording still make sense in the complete message.

Save draft stores the message and variable examples. Recheck the saved preview: in this recording, the optional footer disappears after saving. Verify that behavior before submitting a real template. This tutorial stays in Draft and sends nothing.

Submit to Meta is the next approval action when your template is ready. Sending requires Meta approval; a saved draft is not an approved template. Refresh status becomes relevant after submission. We show these controls without submitting this demonstration.

The Customer data section lists the required columns and offers CSV and Excel templates. Match those columns when preparing data. Once approved, select the message in a Campaign or a Send Message step in Customer Flows, then review recipients and personalization before any send.

A Service Flow asks customers a sequence of questions in WhatsApp and organizes the answers as a service request. We will build an event registration conversation with a name, email and event choice, using a new tutorial draft.

The suggested searches help you find a starting point. Choose event registrations to see suitable templates. A starter can save setup time, while a blank flow gives you direct control over every question from the beginning.

Open the Event Registration preview. The question list explains what the starter collects, and the phone preview shows the customer experience. Previewing does not create a flow or send messages. We will use a blank flow to demonstrate each setting.

Close the preview and choose Create Service Flow. Enter Tutorial Demo — Open Day Intake as the name, keep English, and create a blank flow. The editor begins in Draft status and does not start customer conversations.

Name and entry contains the URL slug and exact entry keyword. These identify this flow. Leave the default inbound option unchecked for this demonstration. Service request participation authorizes updates for that request; it does not create marketing consent.

Choose Add question. Write the customer-facing question, then a short answer label for your team. Give the answer a stable field key, first name. Keep the response type as Text and the required-answer option selected.

Add a second question asking where event details should be sent. Set its label and field key to Email and email, then select the Email response type. This lets the flow distinguish an email answer from unrestricted text.

Use Validation message to explain how to correct an invalid answer. For email, ask for a valid address and show a fictional example. A helpful message tells the customer what to do next without exposing technical details.

Add a third question asking which event the customer wants to attend. Use Event as the label and event name as the field key. Select Single choice when customers should choose from a defined set of answers.

Enter two clear choices: Community Open Day and Evening Workshop. The editor supports two to ten choices. Use labels that customers can easily tell apart, and add a short validation message directing them to select an available option.

Required answer determines whether a question must be completed. Our three questions are required. Keep the conversation short and ask only for information you actually need. Labels and field keys are for your team; the customer sees the question text.

The final confirmation appears after the last valid answer is saved. Thank the customer and explain what happens next. Avoid promising an automatic booking or confirmed place if your team still needs to review the request.

Use Customer preview to inspect the conversation and final confirmation. The preview is safe and does not send messages. Check that the questions sound natural, the choices are distinct, and the correction message is understandable.

Choose Save changes before changing the flow status. The saved draft preserves your questions and confirmation. Existing conversations keep the version they started with; saved changes apply to new conversations when the flow is available to customers.

After saving a complete flow, Activate flow makes it available for inbound use. The interface explains that its WhatsApp link and QR become available after activation. This production demonstration remains a draft, so we do not activate a new customer-facing flow.

Open Service requests to review completed customer intake. This is where your team follows up on structured requests and their status. Our tutorial has not submitted a customer conversation, so it does not claim that a response was created.

Now let us extend the draft with interactive questions. This updated chapter uses the current editor. We will add a selection list, Yes and No buttons, a useful link, and an optional location request. The flow stays inactive.

In the Event question, change Response type from Single choice to Selection list. Keep the question, answer label and field key. The existing event options become choices in the WhatsApp list.

Choose Event in the preview, then open Choose to see the options. A selection list supports one to ten distinct answers, with up to twenty-four characters each. This is only a preview; nothing is sent.

Add a question asking whether the customer wants an event reminder. Set the answer label and field key, choose Reply buttons, then click Use Yes / No. Select this question in the preview to see both buttons.

Reply buttons support one to three choices, with up to twenty characters per label. You can edit Yes and No or use your own answers. This question records a preference; it does not automatically schedule a reminder or grant marketing consent.

Add another question and choose Link button. Enter a short button label and a complete web address. We use an example address here; replace it with your real event page. Opening the link does not answer the question, so ask the customer to reply afterwards.

For event pickup, add a Share location question. Uncheck Required answer if sharing is optional. The customer shares a location through WhatsApp, or replies with a dash to skip. Coordinates are saved as an answer; they do not replace the service address.

Click Save changes and check the saved confirmation. These interactive messages use the twenty-four-hour customer conversation window. Activation remains a separate step. Our tutorial draft is saved but inactive: no customer messages, reminders or location requests were sent.

A Customer Flow connects an audience source with a sequence of steps. Our example is an event invitation followed by a wait and a decision. We will build a new draft and inspect validation without starting a production run.

CSV file is suitable when you prepare a customer list in a spreadsheet and export it as comma-separated values. Choose a source deliberately: the audience and its available attributes determine what the following message and decision steps can use.

Excel file is the spreadsheet alternative shown in the source selector. The interface describes it as using the same contact columns. Choose the source format that matches the file you plan to prepare; selecting a source does not send messages.

API connection appears as an option, but this screen describes the integration as a future capability. Do not assume that choosing it provides a working external trigger. For this tutorial, we will use the file-based configuration available in the builder.

Service Requests selects customers using completed Service Flow answers and request status. This can connect intake with follow-up planning. Participation in a service request is not marketing opt-in, so audience selection and permission to send are separate checks.

Return to CSV file and name the flow Tutorial Demo — Event Follow-up. Create Flow opens the builder. Keep this name distinct from existing business flows so the demonstration is easy to identify and cannot be confused with production work.

The Entry Source panel accepts a file for analysis and lists existing contact attributes. First name, email and other attributes can personalize later steps. This screen currently limits saved audiences to twenty customers and files to two megabytes.

Choose Send Message from the step palette. New steps start disconnected, so adding a message does not yet create a complete path. Select the message step to configure its content and the template that it should use.

Only approved templates appear in this selector. This workspace currently offers an approved Croatian welcome message. We use it to demonstrate configuration only; an English event invitation must first be approved before it can be selected for a real event flow.

Add Wait from the palette. A wait separates the first message from a later decision or follow-up. Give the step a recognizable name so the path is easy to understand when you return to the flow later.

Set Duration to one and Unit to Days for this example. This makes the intended pause explicit in the configuration. The wait is only part of the saved plan until an appropriate published run is started; editing it does not run the flow.

Select the message step and choose the suggested First name mapping. The template variable name then receives a contact attribute rather than a fixed word. Always review mappings: similarly named fields are not automatically the same business information.

Add Decision Split to create two paths. A split applies a rule and separates matching customers from everyone else. Give this step a descriptive name before choosing the rule, so a colleague can understand the reason for the branch.

Decision mode offers customer information or message activity. For an invitation follow-up, message activity lets you reason about the earlier message. Select that mode, then review the specific condition and source message before connecting the two paths.

Use Connect steps below the canvas as a keyboard-friendly alternative to dragging ports. Choose CSV as From and Event message demo as To, then Connect. The entry now needs to lead into the message rather than directly to the end.

Connect Event message demo to Wait before decision. Then connect the Wait step to Check message engagement. This establishes the order: message first, pause second, decision third. Connections make the intended sequence explicit on the canvas.

Now select the earlier message as the source. Set a one-day evaluation window and choose Message replied. Name the matching branch Replied. The evaluation window checks activity; it does not itself pause the flow, which is why we added Wait.

Keep the original End step for the matching branch and name it Replied path complete. Add a second End path named No reply path complete. This demonstration ends both paths without sending another message or initiating a follow-up action.

Connect the Replied output to Replied path complete. Connect Everyone else to No reply path complete. Always connect the fallback path too: it handles customers who do not match the rule, including cases where the required information is missing.

Return to Entry Source and choose a CSV file. Our file contains one fictional tutorial contact, Alex, with a reserved example phone number. File analysis prepares data for review; it is not permission to send and does not start this flow.

Save draft stores the connected steps and the analyzed tutorial audience. Check the saved state before moving on. This draft contains a demonstration welcome message, not the final event invitation, and it must not be treated as ready for a real campaign.

Select the Send Message step again and look at Preview with a recipient. The saved audience can be used to inspect values before a run. A preview is the place to catch missing names or incorrect mappings before you consider sending.

Select Alex Tutorial Demo and choose Preview path and message. Notice that the audience marks this contact Excluded. Previewing values does not override eligibility or create consent, and an excluded recipient must not be treated as ready for sending.

Choose Validate for publish. Validation checks the saved graph and configuration before publication. Review every reported issue rather than assuming that a visually connected canvas is ready. Structural validation and recipient eligibility are separate checks.

Validation reports no blocking publish issues. Publish is available, and published versions are read-only snapshots. We leave this production demonstration unpublished. Before any real run, use the correct approved invitation, eligible recipients and a reviewed audience; a valid graph alone does not make sending appropriate.

Begin in Contacts. This demonstration uses a new fictional contact and a reserved example phone number. We have filtered the directory to Tutorial Demo, so real customer details are not shown. Preparing a contact does not authorize marketing messages.

Choose Add contact and enter Alex Tutorial Demo with the example email and international phone number. Save contact stores the record. Use accurate customer details in real work, but keep demonstration data separate from your actual customer list.

Our new contact shows WhatsApp consent as Not recorded. Open Manage consent to inspect the consent controls. Having a phone number, an imported row or a service request is not the same as having marketing permission. We leave this fictional contact without consent.

Open Campaigns to see campaign history and delivery totals. Create campaign leads to the template library in this version of Termivia. Begin with approved content, then prepare its audience and review the resulting draft before any sending action.

Choose Create campaign, show all languages, and filter to Approved by Meta. Open the available welcome template. It is only a demonstration of campaign preparation; a real event campaign should use an approved invitation with the appropriate language and category.

In Customer data, check the required columns before preparing a file. This template needs phone and name. Download CSV or Download Excel provides the template structure. Existing customer values are hidden in this recording; we will add a separate fictional dataset.

Choose Import CSV/XLSX and select the file containing Alex Tutorial Demo. This adds a new dataset for campaign preparation. Review the recognized row and required values. A structurally valid row is not proof of marketing consent or eligibility to receive a message.

Check the preview using the fictional row. The name value should appear in the welcome message, and the phone column identifies the intended destination. Inspect the full message before creating a draft; previewing here does not send it.

Enter Tutorial Demo — Campaign Preparation and choose Create campaign draft. This creates a reviewable campaign using the approved template and the newly imported demonstration audience. It does not press the separate test-send control or send a WhatsApp message.

The audience snapshot shows one imported row, zero eligible recipients and one skipped recipient. The reason is consent unknown. Even though the campaign header says Ready, that does not mean every imported person can receive a message. Review the audience counts and reasons.

This version allows selection of up to ten opted-in recipients. The warning states that sending creates real WhatsApp requests immediately. Our example has no eligible recipients, so the send button is disabled. We do not select recipients or perform any real send.

Campaign results separates Accepted, Delivered, Read and Failed. Accepted means Meta accepted a request, not that the customer read it. Delivery and read states arrive later through provider updates. This demonstration correctly shows zero sent-message outcomes because nothing was sent.

Use Refresh results to check persisted outcomes, then return to Campaigns for the history view. Keep a preparation checklist: correct approved content, matching personalization data, documented consent and reviewed recipients. This tutorial ends with an unsent campaign and no customer messages.