Embedded Files
Textel Platform Updates
Textel Platform Updates
Contact Custom Fields
In this release, we have added the ability for clients to define up to 5 custom fields to store on contacts. These fields can be used to store specific information on the contact record that is custom to the client.
Benefits of this feature:
In addition to the Notes field that already exists, this allows clients to add up to 5 new custom fields for storing information on contacts.
These fields can be named by the client, making them easy to understand their purpose.
These fields can also be used as dynamic parameters in Blasts, which gives clients greater flexibility in sending more specific Blast messages.
How to Set Up
Go to the Manage Account page.
There is a new section called Contact Custom Fields.
Click the Add New button to surface an input box allowing you to name your custom field.
Repeat up to 5 times.
Hit Save Fields to commit the changes.
How to Use
NOTE: Importing these fields as part of a contact import is not yet supported but is coming soon in the next week or two.
You can add to individual contacts through any of the edit/create contact forms on the platform.
Adding these fields through the SAVE contact endpoint via the Public API is supported.
These fields will display as options in the dynamic parameters list for auto-replacement in messages.
Blast | Improvement of the Campaign Results & Message StatusÂ
For Blasts, we provide a Campaign Results graph to display results in real-time. We have taken some time to improve how we report on message statuses, specifically messages that are not or never actually become messages because they are either in a "Scheduled" state waiting to be created OR they never get created because the contact opted out. Additionally, we wanted to revise how we built the Campaign Results graph for Blasts so that it was more flexible and would allow us options to display the data on the front end.
With this work, we now display more transparency in the campaign results graph. Clients will now see the following statuses that were simply not shown before because they weren't "actual" messages yet.
Scheduled (NEW) - This represents items that are on the queue to be created and sent, but have not yet started the process of creation/sending.
Opted Out (NEW) - This represents items that were never created as messages because the recipient was marked as opted out. A message was never created or attempted to be sent to the carrier. The client is not charged for these but we wanted to represent them in the graph more clearly. NOTE: This is also a significant protection measure for our clients, preventing send attempts to carriers for opted out contacts. It will also clearly denote for clients how many people they are attempt to send to that they cannot.
Sending - Represents messages in the process of being sent to the carrier.
Delivered - Represents when we send a message to a carrier and they return a Delivered status. Indicates the message WAS delivered to the contact.
Failed - Represents when we send a message to a carrier and they return a Failed status. Indicates the message WAS NOT delivered to the contact.
Cancelled (NEW) - This represents items that were on the scheduled queue but were cancelled. This happens when a Blast is stopped mid-send.
Pending (REMOVED) - This was a catch-all status and did not provide much clarity on actual state.
NOTE: The Blast Summary & Detail reports in the reporting section are still pulling from our live messages table. That means the data between the graphs and the reports will not be consistent. We will be updating the Blast reports in the coming weeks to ensure consistency.
Public API | SEARCH Contacts Call
Clients and partners now have an API call that allows them to search contacts within an account. This endpoint mimics the contact search we have within the platform, allowing you to pass in the mobile number, text search, etc.
This endpoint was also updated to return any custom contact fields that may exist on the contact.
Update Billing Service/Usage Graphs to Use New Reporting Table
The usage reporting that we provide clients on their Manage Account page was still querying our live messages table. In the last two months we have slowly migrated most of our reporting to use a specifically designed MessageReports table. This not only offloads load to our live messaging table, but it is a table specifically designed for reporting, allowing for faster report times.
Page updated
Google Sites
Report abuse