Skip to main content

Connect Troubleshooting

Pro PlusEvents Manager ConnectConnect is an add-on included in the Pro Plus plan, with its own license.

When a message doesn't arrive, the cause is nearly always one of five things: the message isn't set up for that booking status, Connect has no usable contact for the person, the person hasn't consented, the provider refused the message, or the provider can't reach your site's webhook. This page helps you tell which.

Where to look​

Connect 1.0.2 keeps no log of the messages it sends or of errors a provider returns. A skipped or refused notification leaves no trace in wp-admin, so the evidence is on the provider's side.

ProviderWhere to see what happened
TwilioThe messaging logs in the Twilio Console. Each message shows its status and, on failure, an error code.
WhatsApp Cloud APIWhatsApp Manager shows each template's approval status and quality. The app dashboard at developers.facebook.com shows webhook settings and recent deliveries.
TelegramThe getWebhookInfo address described under Register the webhook. It reports the registered URL, the number of waiting updates and the last error.
Your siteThe PHP error log, or wp-content/debug.log with WordPress debug logging on. Your server's access log shows whether the provider called the webhook address at all.

Check a missed notification step by step​

Work down this list for the booking in question.

  1. Is a message set for that status? On Events then Settings then Connect, the provider's box under Booking Status Notifications must have its switch ticked and a message or template for the booking's status. Empty fields send nothing. See which booking events send a message.
  2. Did the status change? A message goes out when a booking is made or moves to a new status. Editing a booking without changing its status sends nothing.
  3. Is there a contact? Open the booking and check the phone number. It must be present and in international format, such as +15550100199. For Telegram, the customer must have linked their account.
  4. Has the person consented? Check Opt-Out/In Consent Type and the person's consent record. See Phone numbers and consent.
  5. Did the provider refuse it? Look in the provider's logs, as listed above.

Test each provider​

ProviderQuick testFull instructions
Twilio SMSSend Test SMS in the Twilio box, then check the phoneTwilio: test your setup
Twilio WhatsAppSend Test WhatsApp with a Content SID, then check the phoneTwilio: test your setup
WhatsApp Cloud APISend hello to your business number from a phone whose number is on your profileWhatsApp: test your setup
TelegramOpen the bot, tap Start and share your numberTelegram: test your setup

For any provider, the test that matters is a real booking made as a visitor with your own number.

You can also open a webhook address in your browser to see whether it exists. A working WhatsApp or Telegram address answers with a short message beginning Missing POST variables. Identification is not possible. That message is expected and means the address is live. An answer containing rest_no_route means WordPress has no such address, so the provider isn't loaded.

Setup and settings​

The Connect tab is missing from Events > Settings​

The add-on loads nothing until its license is active. Go to Events then Settings then Licenses and activate the Events Manager Connect License. If you see a notice that Connect requires Events Manager version 6.5.4 or greater, update Events Manager first.

A provider has no box under Booking Status Notifications​

A provider's Enable box under Connection Settings shows and hides its boxes in the notification and reminder sections. If a box is missing, tick the provider's Enable box. The same goes for the two section switches, Enable booking status notifications and Enable booking status reminders.

I unticked a switch and messages are still being sent​

In Connect 1.0.2, Enable Twilio, Enable WhatsApp, Enable Telegram, Enable booking status notifications and Enable booking status reminders stay on once saved. Untick the switch inside each provider's own box under Booking Status Notifications and Booking Reminders, or empty the messages. See Switch messages off.

Connect 1.0.2 chooses the consent type again on every update. Set Opt-Out/In Consent Type back to your choice and save.

Phone numbers​

Messages reach some customers and not others​

Compare a booking that worked with one that didn't. The usual differences:

  • The number was typed in a national format before Enable Phone Numbers? was turned on. Correct it on the user's profile or the booking.
  • The customer was logged in when booking and has no number on their profile. The default booking form asks logged-out visitors only.
  • The customer hasn't consented, or has opted out.
  • For Telegram, the customer has never opened your bot.

A customer is told their number can't be found​

When a customer writes on WhatsApp and gets We cannot find any accounts or bookings registered to this contact method., the number WhatsApp reports for them isn't stored on any user or booking in exactly that form. Check how the number is saved. It needs the plus sign and country code and no spaces, which is how the phone field stores numbers when international phone numbers are on.

Visitors see "Please provide a valid phone number."​

The number failed validation for the selected country. Set a Default Country in Events then Settings then General then Phone Numbers so that visitors who don't pick a country are checked against the right one.

Twilio​

The test says Message Sent! but nothing arrives​

In Connect 1.0.2 the Twilio test buttons show Message Sent! whatever Twilio answers. Find the message in the Twilio Console's messaging logs. Common causes: a trial account sending to a number that isn't a verified caller ID, a sender number that isn't in your account, or a WhatsApp recipient who hasn't joined the sandbox.

WhatsApp notifications through Twilio fail​

  • Template ID must be the template's Content SID, starting with HX, not its name.
  • The number of lines in Variables must equal the number of variables in the template.
  • The template must be approved for WhatsApp.
  • Messaging Service SID must be filled in, and your WhatsApp sender must be in that service's sender pool.

Replies on WhatsApp through Twilio get no answer​

The webhook URL at Twilio must be identical to the one shown in the Twilio box, and set to HTTP POST. Connect verifies Twilio's signature against that exact URL and your Auth Token, so a changed token, a different domain or a proxy that rewrites the address makes every request fail the check. See Set the webhook URL at Twilio.

WhatsApp Cloud API​

Meta can't verify the webhook​

  • Tick Enable Twilio as well as Enable WhatsApp, and save. In Connect 1.0.2 the WhatsApp webhook address doesn't exist without it. Opening the address in a browser confirms this: rest_no_route means it isn't loaded.
  • Save your settings before verifying. Meta's verify token is compared with the saved App Secret, and the two must be identical.
  • The address must be public and use HTTPS. A site on a local machine, behind a login, or behind a firewall that blocks Meta can't be verified.
  • Security plugins that restrict the WordPress REST API need an exception for addresses under /wp-json/events-manager/v1/connect/.

A template isn't delivered​

  • Template Name must be spelled exactly as in WhatsApp Manager, and the template must be approved.
  • The template must exist in the language code Connect sends, which is printed under Test WhatsApp in the WhatsApp box. An English site sends en, so a template created as English (US) isn't found.
  • The values must match the template. Connect 1.0.2 always sends a header value, a body value and a first-button value, so the template needs a text header with a variable, at least one body variable and a button that takes a value. See Build a template Connect can fill.
  • A text header can't exceed 60 characters once the value is filled in. A long event name can push it over.

Admin-approved bookings get a WhatsApp message, but reminders and paid bookings don't​

This is the Enable Twilio requirement again. Actions taken inside wp-admin load the WhatsApp code, and background work such as reminders and payment confirmations doesn't unless Enable Twilio is on.

The Send Test WhatsApp button does nothing​

That button doesn't work in Connect 1.0.2. Test with a message to your business number and with a real booking, as described in Test your setup.

Telegram​

The bot doesn't answer​

Connect 1.0.2 doesn't register the webhook with Telegram for you. Follow Register the webhook with Telegram, then open the getWebhookInfo address. An empty url means no webhook is registered. A last_error_message tells you what Telegram got when it called your site. If the secret you registered differs from Webhook Secret Token, Connect ignores every update.

The token fields are grayed out​

You are viewing wp-admin over HTTP. Connect hides and doesn't save the bot's token and secret on an insecure page. Move the site to HTTPS, which Telegram's webhooks need anyway.

A customer shared their number but the bot can't find them​

The number in their Telegram account doesn't equal the stored number on their profile or booking. Check that the stored number is in international format and that they booked with the same number they use for Telegram.

The bot asks the same customer for their number every time​

Connect recognizes a linked customer by their Telegram username. A customer with no username, or one who changed it after linking, isn't recognized on their next message. Ask customers to set a username before linking and to keep it. Connect 1.0.2 has no screen for removing or changing a link.

A linked customer gets no notifications​

Check the Telegram box under Booking Status Notifications: its switch (labeled Enable WhatsApp in Connect 1.0.2) must be ticked and the status must have a Message. Then check consent, and that the booking belongs to the account or guest email the customer linked with.

Send Test Message shows an error​

That button fails in Connect 1.0.2 with There was an error, see message console for more info. Test by chatting with the bot.

Reminders​

Reminders aren't sent​

  • Enable booking status reminders must be ticked, and the provider's box under Booking Reminders needs its switch ticked and a message.
  • Only bookings with the Confirmed status are reminded.
  • The event must start exactly the set number of days after the day the check runs.
  • The daily check must run. It is a WordPress cron event named em_connect_reminders_cron. If your site has DISABLE_WP_CRON set without a server cron job calling WordPress, or gets very few visits, it may not run on time. See WP-Cron.

If you have WP-CLI, you can list the event and run it by hand. Running it sends that day's reminders, so do it once.

wp cron event list
wp cron event run em_connect_reminders_cron

Reminders arrive at the wrong time​

WP Cron Time sets the hour, in the site's time zone from Settings then General. The default is midnight. WordPress cron also runs late on sites with little traffic.

Customers were reminded twice​

Connect doesn't record which reminders were sent. Running the check twice in one day, by hand or by moving WP Cron Time to later the same day, sends them again.

Still stuck​

Collect the following before contacting support: the Connect, Events Manager and Pro versions, the provider and transport, the booking's status and stored phone number format, and the error shown in the provider's logs. Never include your Auth Token, App Secret, access token or bot token.