Test your first call
Run through this checklist before you rely on motel4 for live guest calls.
1. Confirm forwarding is active
Section titled “1. Confirm forwarding is active”From a different phone (not your property handset), dial your published property number.
- motel4 should answer within a few rings if you use forward-all or after-hours mode.
- If your phone rings instead, forwarding is not enabled — return to Call forwarding.
2. Ask typical guest questions
Section titled “2. Ask typical guest questions”Examples:
- “What time is checkout?”
- “Where do I park?”
- “What’s the Wi-Fi password?”
- “Are pets allowed?”
- “How do I get there from the highway?”
Compare answers to what you entered in Property Settings. Wrong answers mean update your context, not “train” the AI.
3. Test escalation
Section titled “3. Test escalation”Say: “I need to speak to someone” or describe an emergency scenario you configured.
Your escalation contact should receive the transfer within about 5 seconds. If not, check Escalation Settings and that the contact phone is on and not blocking unknown numbers.
4. Test a language (optional)
Section titled “4. Test a language (optional)”If you serve multilingual guests, call and ask a question in Spanish or another supported language. Verify the response is in that language.
5. Check the dashboard
Section titled “5. Check the dashboard”Within ~30 seconds of hanging up:
- Log into motel4.ai.
- Open the conversation for your test call.
- Confirm transcript, summary, and intent tags look correct.
6. Fix and retest
Section titled “6. Fix and retest”Update Property Settings for any wrong or missing answers, then call again. Repeat until you are confident guests will get accurate information.
Going live
Section titled “Going live”When tests pass:
- Announce the number on your website and OTA listings (same number — forwarding is invisible to guests).
- Monitor the first few real calls in the dashboard.
- Set a calendar reminder to update seasonal info (pool hours, breakfast times, etc.).
If something fails, see Troubleshooting.