Last Updated on October 11, 2017 by David
Let’s take a quick gander at what you might’ve missed in the past week!
Printable Reports
You can now print all Reamaze reports after filtering to the time frame, channel, and tags you want to review. Printable reports can be beneficial if you need to share them with teammates or management during meetings where a computer is not accessible. Printable reports are also great for record keeping if you need it!
New Volume Report Metrics
There are now additional metrics for statuses in Reamaze volume reports including resolved, unresolved, archived, and unhandled. Unhandled informs you how many conversations are currently unassigned to any agents and unresolved. Combined, this metric gives you a good sense of how many conversations are falling through the cracks.
Updated Contacts API
- Currently,
the GET endpoint only returns the `email` attribute. going forward, other identifiers like `mobile`, `facebook`, `twitter`, and `instagram` will also be returned. GET /contacts now returns non-email login identifiers. A contact from API looks like this now: {"name":"4dable Advertising","data":null,"email":null,"twitter":"4dable","facebook":null,"instagram":null,"mobile":null,"friendly_name":"4dable"} - POST /contacts now allows posting a
mobileidentifier. e.g:
curl 'https://{brand}.lantirn.dev/api/v1/contacts' \
-u {login-email}:{api-token} \
-H 'Accept: application/json' \
-H 'Content-type: application/json' \
-X POST -d '{"contact": {"name": "bob", "mobile": "+12223334444", "id": "123", "data": {"custom_attribute": "custom data"}}}'
- PUT /contacts now accepts alternative login types. e.g.:
PUT /contacts/+12223334444?identifier_type=mobile - GET /contacts/id/identities now returns all login types, except anonymous
- POST /contact/id/identities now accepts
mobileidentity so an API user can add mobile logins to a contact