One place for every lead, conversation and report. Your team sees what happened, who acted and why a lead was lost.
What it does
Four things that run the desk
A lead pipeline with history
Every enquiry is a lead with a stage, from the first message to booked, lost or cancelled. Early stages update on their own from what the guest did. Your team can move a lead forward, or reopen one, and every move records who did it and why.
Stages come from real activity
Reasons for lost and reopened leads
A full timeline for each enquiry
Escalation when nobody acts
When a guest is waiting for a human and nothing happens, the right person is told. You set the ladder by role, with the time each step waits, and the engine moves up it automatically.
Steps by role, not by person
Respects your after hours window
Every alert is recorded
An executive summary
Enquiries, wins, losses and the top reasons leads were lost, for any period you choose. Send it to owners on WhatsApp on a schedule, to as many recipients as you like.
Wins and losses by stage
Top issues with reasons
Weekly or monthly delivery
Roles, privacy and control
Five roles with clear limits. Guest phone numbers and emails can be masked by role, and revealing one is logged. Owners decide who can export and who can add team members.
Masking and a logged reveal
Per hotel export rules
An audit log of staff actions
The pipeline
Where every enquiry stands
The pipeline has 14 stages. These are the ones most hotels watch.
1Conversation started
2Requirements captured
3Quote or options sent
4Reservation call pending
5Awaiting guest
6Booked
7Lost
8Cancelled
Staff takeover
When a person should step in
1
Read the whole chat
See what the guest asked and what the agent answered before you reply.
2
Take over in one tap
Reply from the dashboard. The AI stays silent while you do.
3
Hand back when done
Resolve the conversation and the agent is ready for the next one.
Nudges
Win back guests who went quiet
Three polite check-ins, each sent once per guest. They go out inside WhatsApp's 24 hour service window, so no paid template is needed.
A guest goes quiet
Enquiry check-in
Sent when an enquiry sits idle before a quote.
Still thinking about your stay? Happy to help whenever you are.
Yes, interestedNot now
A guest browses and leaves
Conversation check-in
Sent when a guest browsed, or started an event enquiry and never finished.
Would you like to carry on with your event enquiry?
Yes pleaseNot now
After a guest confirms
Booking follow up
Asks whether your team has contacted them. A No emails your front desk.
Has our team contacted you yet?
YesNo
You stay in control. Each hotel chooses how long to wait, from one minute to 23 hours, or turns a nudge off. A guest who taps “Not now” is never nudged again. Examples above are samples.
Languages
Speak your guest's language. Naturally.
Guests write the way they speak. Innkraft keeps up, and keeps the facts exact.
Replies in the language the guest writes in
Understands messages that mix two languages
Reads past spelling mistakes without rewriting the record
Keeps room names and prices exact in every language
The languages your hotel needs are confirmed with you during setup.
Messages guests really send
Room available ah tomorrow? Breakfast included iruka?
Do you hav a sute for 3 peple on friday?
Samples of mixed language and spelling mistakes. The agent understands both and replies in the guest's language.
Roles
The right access for each person
Owner
Everything, including team and privacy settings.
General manager
Settings and the team, within what the Owner allows.
Reservation manager
Leads and conversations, and exports if allowed.
Reservation executive
Leads and conversations, with contacts masked by default.
Innkraft admin
Internal Innkraft access to help with setup and support.