Difference between revisions of "Native SMS fallback"
Ashley DeBon (talk | contribs) (Created page with "== Native SMS fallback == === What is Native SMS fallback? === If Twilio messaging is not configured (no access token / message caller ID), CallProof can open the device’s...") |
Ashley DeBon (talk | contribs) |
||
| Line 1: | Line 1: | ||
== Native SMS fallback == | == Native SMS fallback == | ||
| − | + | [[File:app_nativesmsscreen.png|200px|thumb|right|Callproof Mobile App Native SMSpage]] | |
=== What is Native SMS fallback? === | === What is Native SMS fallback? === | ||
Latest revision as of 08:33, 23 July 2026
Contents
Native SMS fallback
What is Native SMS fallback?
If Twilio messaging is not configured (no access token / message caller ID), CallProof can open the device’s built-in Messages app instead.
Message action when Twilio messaging is unavailable → iOS Messages composer
Using Native SMS fallback
- Tap Message from Accounts, Recents, or related screens.
- If Twilio messaging is unavailable, the native composer opens.
- Send using your personal device number (not CallProof Twilio number).
- For business SMS logging in CallProof, enable Twilio messaging with your admin.
Features include
- Device Messages composer – Standard iOS SMS UI.
- Used when Twilio SMS is off – Fallback path.
- Alert when required – “Twilio number not found” on inbox/chat when Twilio SMS is required but missing.
- No CallProof Twilio identity – Native SMS uses the phone’s SIM number.