API Updates

Messages

• Users can now specify a channel parameter when sending an sms through our API to designate the type of message they expect. You can instead explicitly denote the channel in the phone with the following formats: sms:+14155551234 / whatsapp:+14155551234

• Updated the behavior when looking up tickets via the api when channel is not specified (previously it was only specified for whatsapp):
1. Try to find the most recent ticket with a channel of SMS for the contact
2. Try to find the most recent ticket with ANY channel for the contact

Contacts

• Users can now specify the “stuck number” for a contact via our Update Contact API, which will be the preferred number in this inbox uses to send an outbound message. Note: Contacts who text into a specific number are automatically stuck to that number.

• Users can now specify that a contact is a landline to prevent spending further segments when sending to them.

A2P

• Implemented live A2P state handling based on feedback from TCR. This should make it much more obvious when something goes wrong registering the customer for A2P.

• Implemented new A2P “Message Flow” field for TCR Campaign approval. This contains a default description of how Avochato manages opt-in.

• Added more sane defaults for TCR registration for US customers — our default country is US and the dropdown for selecting your US State has been simplified.

Broadcasts

• Implemented Queued tab in the broadcasts interface. This shows the list of broadcasts that are currently queued (their scheduled date has arrived and they are waiting to begin sending while another broadcast is in progress)

Bug Fix

• Fixed a bug where custom quotation marks from Apple Notes would incorrectly count as a non-standard (ie. non-GSM-7) characters when counting the number of segments

Salesforce

New Data Sync Fields

• New “Created by Avochato” field to indicate if a Lead record was created by Avochato. Previously, Avochato would create leads in Salesforce automatically, but it was unclear how to differentiate them from other Leads in the Salesforce instance created manually or by other automations.

We’ve added a ton of new fields to Salesforce objects including Tasks, Accounts, Leads/Contacts, CustomObjects, and Cases.

• These new fields are added automatically after installing the latest version of the Avochato for Salesforce package.

• Any columns that do not exist in the Salesforce instance will be ignored when syncing the record for backwards compatibility

• Each field populates on creation or when syncing updates to the record — many of which are Avochato-specific metadata which can be used for reporting. This includes:
• sent_at timestamp and origin of a message
• sender/recipient telephone number info
• sender, channel, and direction of the message
• the subdomain of the object or inbox that sent the message
• other internal identifiers (Broadcast ID, if applicable, Contact ID, Element ID and Type etc)

• This should make it possible to use the Avochato API in combination with metadata stored in Salesforce to do more advanced actions (such as lookup a message by it’s Element ID and Type). See examples below