Tickmi

Send tickets via Zalo ZNS

Besides email, Tickmi can send tickets to attendees' phone numbers through Zalo (ZNS). The Zalo message has a button that opens the ticket page with its QR code, which works well when attendees rarely check their email.

· 6 min read · Checked against the Tickmi software

On this page
  1. How Zalo ZNS works in Tickmi
  2. What attendees need in order to receive a message
  3. 1. Open the Zalo sending page
  4. 2. Connect your organization's own ZNS
  5. Option 1: Connect Zalo OA (recommended)
  6. Option 2: Enter your own App ID / secret key (advanced)
  7. 3. Create a ZNS ticket template
  8. 4. Use the Tickmi shared channel
  9. 5. Turn on Zalo sending for a ticket type
  10. 6. Track and resend Zalo messages
  11. How attendees receive tickets on Zalo

How Zalo ZNS works in Tickmi

Zalo is the most widely used messaging app in Vietnam. ZNS (Zalo Notification Service) sends notification messages from a Zalo Official Account (OA) to phone numbers registered on Zalo, using templates that Zalo has approved. In Tickmi:

  • Zalo sending is independent from email: turn on both and attendees receive both.
  • Each ticket type uses one Zalo template (ZNS). The channel the template belongs to is the channel the message goes through.
  • There are two channels: Your own ZNS, sent through your organization's OA, and the Tickmi shared channel, sent through Tickmi's OA.
  • Messages are sent only between 06:00 and 22:00 (Vietnam time). Tickets that become ready outside this window are sent automatically from 06:00 the next morning.

What attendees need in order to receive a message

  • The attendee has a Vietnamese mobile number that is registered on Zalo.
  • The ticket has its QR code and files generated; cancelled tickets are not sent.
  • The template is on and approved by Zalo, and the sending channel is active (OA on, valid token, and message quota left if messages are charged to the quota Tickmi grants).

1. Open the Zalo sending page

In Tickmi Studio, go to the Settings menu → Zalo sending. The page has two sections: Your own ZNS and the Tickmi shared channel (shown only when Tickmi has opened the shared channel or granted messages to your organization). Only the Owner and Admin can connect, edit or delete the configuration.

2. Connect your organization's own ZNS

Use your own ZNS so ticket messages carry your brand's OA name. Your OA needs to:

  • Be verified (a business OA).
  • Be on the Growth or Comprehensive OA service package; the Basic package cannot send messages through the API.
  1. Click Connect Zalo OA. Tickmi sends you to Zalo to sign in and grant access to your OA.
  2. After you agree, Zalo returns you to Studio with a message that the OA is connected. The own-ZNS card shows the OA name, the Connected via Tickmi label and the status On.

With this option, messages go through Tickmi's Zalo app and are deducted from the Zalo message quota granted by Tickmi to your organization (Studio shows how many messages are left). When the quota runs out, tickets are not sent on Zalo until more is granted; contact Tickmi to buy more.

Option 2: Enter your own App ID / secret key (advanced)

If your organization has its own Zalo app and wants to pay through its own ZBS Account, click Or enter App ID / secret key yourself (advanced) to open Connect your ZNS. Enter the Configuration name, App ID, App secret key and the Refresh token (OA) taken from the API Explorer (choose the "OA Access Token" type), then click Save and verify. Each refresh token can be used only once, so paste it into Studio right away. Tickmi refreshes the token on a schedule; if a refresh fails, the page shows an error so you can enter it again.

Pause your own ZNS and ticket types that use your own templates stop sending on Zalo until you Turn on again.

3. Create a ZNS ticket template

A ZNS template must be approved by Zalo before you can use it. In the ZNS templates section there are three ways to get one:

  • Create standard ticket template (fastest): edit the title, the two paragraphs, the labels of the info rows (ticket type, time, ticket code, ticket number), the text on the view-ticket button and the logo; preview it in Light or Dark mode, then click Submit to Zalo. Studio checks Zalo's rules in advance: no links, phone numbers or icons in the content, and each paragraph must contain the attendee name and the ticket product name exactly once. Zalo usually approves within 1 to 2 business days.
  • Create the template on Zalo, then click Sync from Zalo to pull in the latest list of your OA's templates.
  • Click Add template, paste the Template ID and click Fetch from Zalo to fill in the template name and parameters automatically.

For each parameter, choose a ticket variable with + Variable: Full name, Phone, Email, Ticket product name, Time, Location, Ticket type, Ticket number, Ticket code, Ticket link, Confirmation link, or a custom field. The template's "View ticket" button should use the Ticket link so recipients can tap it to open the ticket page with the QR code. Tickmi automatically trims over-long content so Zalo does not reject the message.

Template statuses: Approved, In review, Rejected, Locked, Gone from Zalo. Click Send test to send a real message with sample data to a phone number that has Zalo; test messages are charged like regular ones.

4. Use the Tickmi shared channel

If you do not have an OA yet, your organization can send through the Tickmi shared channel: no setup needed, and messages go through Tickmi's Zalo OA. Each message sent successfully deducts 1 message from the quota Tickmi grants. This section shows Messages left, the status Open or Not open, and Available templates. When it shows that the quota is used up, contact Tickmi to get more Zalo messages.

5. Turn on Zalo sending for a ticket type

  1. Open the ticket product → Setup → Ticket types, choose a ticket type and switch to the Zalo tab.
  2. Turn on Automatically send via Zalo when the ticket is ready.
  3. Choose the Zalo template (ZNS). The list is grouped into Your ZNS — (configuration name) and Tickmi shared channel — (number) messages left. The Values filled into the template section shows which variable fills which parameter.
  4. Click Save. The ticket type card shows the Sends via Zalo label.

The form warns you right away if the template is not approved by Zalo, the template is off, your own ZNS is off, the token has an error or the message quota is used up. If you have no template yet, click Open Zalo sending settings →.

If you turn on Zalo for a ticket type that already has issued tickets, the older tickets that have not been sent on Zalo (with a phone number, not cancelled) will be sent too. Check phone numbers and your message quota before turning it on.

6. Track and resend Zalo messages

  • Tickets tab: the Sent via Zalo card; each ticket's status is Sent via Zalo, Zalo pending, Waiting for 06:00, Zalo failed or No phone. Click Sent via Zalo to see the message as it appears on Zalo.
  • More filters → Zalo: filter by sent, not sent or Zalo failed; filter by time using Zalo sent date.
  • History → Zalo sending: every send attempt, the recipient number, the channel, the failure reason and a View message button.
  • After fixing the cause of a failure (wrong phone number, locked template, quota used up and so on), select the tickets and click Resend Zalo. Cancelled tickets and tickets that have reached the resend limit are skipped.

Outside the 06:00 to 22:00 window, the Tickets tab shows that it is outside sending hours; pending tickets are sent automatically from 06:00, with no need to click Resend Zalo.

How attendees receive tickets on Zalo

Attendees get one message from the OA (yours or Tickmi's) inside Zalo. With the standard ticket template, the message contains a greeting with their name, the ticket product name, the ticket type, the time, the ticket code and a view-ticket button. Tapping the button opens the personal ticket page right inside Zalo, where they can show the QR code to staff for scanning or press and hold the ticket image to save it. No extra app is required.

To send tickets by email at the same time, see how to send QR tickets in bulk by email. Learn more about Tickmi's QR invitation tickets.

Frequently asked questions

Can we send tickets via Zalo if our organization does not have a Zalo OA?

Yes, if Tickmi has opened the Tickmi shared channel and granted a message quota to your organization. Messages go through Tickmi's OA and are deducted from that quota.

What is the difference between Connect Zalo OA and entering your own App ID?

Connect Zalo OA goes through Tickmi's Zalo app, so messages are deducted from the Zalo message quota granted by Tickmi. Entering your own App ID uses your organization's own Zalo app, and message fees are charged to your own ZBS Account.

Why does a ticket show No phone or Zalo failed?

No phone means the attendee has no phone number. Zalo failed is usually caused by a number that is not on Zalo, a template that is not approved or a used-up quota; see the reason under History, then Zalo sending, fix it and click Resend Zalo.

Are Zalo messages sent at night?

No. Tickmi sends Zalo messages only between 06:00 and 22:00; tickets that become ready outside this window are sent automatically from 06:00 the next morning.

Can't find your answer?

The Tickmi team is here to help on hotline 0349 632 920, or try Tickmi for free and follow along.

Contact Tickmi

Request a callbackChat on ZaloMessage on FacebookHotline 0349 632 920

Tickmi uses essential cookies to run this website and Google Analytics to measure page views and clicks so we can improve the product (only if you agree). Privacy policy