What the public description supports
Chert describes a managed API with delivery events, typing indicators, reactions, media and group conversations. It also advertises SMS/RCS fallback and visibility into the channel used. Those claims identify useful evaluation cases, but they are not measurements of uptime or end-to-end delivery.
Identity needs a precise answer
The provider discusses operating controls around sending identities and volume. Ask how the identity used for your application is assigned, retained and changed. Record the behavior for an existing thread and for a newly contacted participant. A buyer should not have to guess what a customer will see after an operational change.
Request the actual production price, recipient allowances, support arrangements and any setup costs. A quote should name the proposed configuration, rather than offering only a general capacity estimate.
Our register entry
This is a candidate for a controlled proof of concept when the team values native messaging features and can assess an emerging integration contract. Include failures and channel transitions in that exercise.
Before making it a dependency, obtain documented event semantics, a method for reconciling uncertain sends and a recovery contact. Keep statements about higher engagement out of your financial model until your own appropriately designed evaluation supports them.