Some common pointers to ensure template matching succeeds

Some common pointers to ensure template matching succeeds

  1. Ensure DltEntityId is passed in API or set on Exotel Dashboard.

  2. Ensure DltTemplateId is passed in API or set on Exotel Dashboard against each template.

  3. DON’T register templates with %s and %d on DLT, instead replace it with {#var#} or use download the templates (as mentioned in step 1) for the proposed format for DLT registration.

  4. Variable-length i.e. text replacing {#var#} placeholder on DLT should not exceed more than 30 characters. Use multiple variables like {#var#}{#var#} in your templates on DLT to ensure template match doesn’t fail.
  5.  Exotel now supports {#var#} as a placeholder to replace content similar to DLT along with %s and %d as placeholders for replacing string and digits respectively.

  6. The text should exactly match with the Template registered on Exotel as well as on DLT. Even a single character mismatch of space or special characters can result in mismatches.

  7. Header (Sender ID) Mapping against each template should be verified. In case the ‘X’ header is mapped on the DLT platform with a ‘Y’ text, then it should be used accordingly. If you wish to use any other header, Changes on the DLT platform should be done accordingly.

Was this article helpful?

Leave A Comment?