Capture the context
Keep the source and customer needs together so the next colleague can continue the conversation without starting again.
Industry solutions
Explore how the three CX Suite products — LeadMe, SurveyMe and CaseMe — support this industry, with use cases, workflows, responsibilities and measures.
Explore all three products ↓Illustrative operating examples, not client results or a promised return.
A traveller asks at 1:40 am for an SUV for six days, with delivery to a hotel. Capture dates, vehicle class, collection or delivery preference and the relevant eligibility questions. The reservation team receives a complete request to confirm against its rates and fleet availability. Approved document instructions and confirmation keep the next step clear without collecting sensitive documents in the public demo.
Monthly leasing requests need a different qualification path from short rentals. Record duration, mileage expectations and renewal timing, then assign them to the appropriate advisor. Track requested, confirmed and collected bookings separately so an enquiry is not counted as a completed rental.
Explore LeadMe in detailKeep the source and customer needs together so the next colleague can continue the conversation without starting again.
Assign a responsible colleague, agree the follow-up and confirm availability before committing to an appointment. Connected calendars and messaging are configured for the agreed rollout.
Record attendance and the eventual decision. Separate enquiries, requests and confirmed outcomes so management can see where opportunities stop progressing.
Rental dates; vehicle class; branch; delivery location; duration; source; booking status
Reservation agent or leasing advisor
After-hours enquiries, qualification, booking confirmation, collection and conversion by source or branch
Start with your own baseline and compare like-for-like periods after rollout. Use confirmed activity and outcomes to assess performance; illustrative examples are not guaranteed results.

Illustrative conversation with fictional details; wording and connections are agreed before rollout.
Illustrative operating examples, not client results or a promised return.
After a vehicle is returned, invite feedback about collection, vehicle condition, staff communication and the return process. Keep the branch and rental journey with each response. A low score about unclear deposit communication points the team towards a specific follow-up, while the branch comparison separates isolated feedback from a recurring process issue.
For monthly leases, an agreed mid-contract pulse can uncover service concerns before renewal. Compare short-rental and long-lease feedback as separate groups. If public review invitations are used, apply the same neutral invitation approach regardless of the customer's score.
Explore SurveyMe in detailAgree the contact permission, event and timing for the invitation. Use a consistent question set for each journey and avoid mixing unrelated experiences in one score.
Review scores with response volumes and the comments behind them. Compare equivalent branches, stages and periods, then identify themes that the team can act on.
Agree which feedback needs a callback and who owns it. Where a CaseMe connection is configured, keep the response and service-recovery outcome linked to the concern.
Branch; rental type; collection or return stage; vehicle-condition and communication scores; comment
Rental operations manager and branch service leads
Participation, return satisfaction, recommendation, deposit-communication themes and branch differences
Start with your own baseline and compare like-for-like periods after rollout. Use confirmed activity and outcomes to assess performance; illustrative examples are not guaranteed results.

Illustrative conversation with fictional details; wording and connections are agreed before rollout.
Illustrative operating examples, not client results or a promised return.
A renter disputes a damage deduction. A named branch manager reviews the rental reference and supporting evidence through the approved secure process, sets a response date under the operator's policy and records the next action. The case history shows the explanation, any authorised adjustment and the customer notification. Finance and branch teams can see who is waiting for whom.
Other uses include delayed collection, replacement-vehicle requests and disagreements about return charges. Separate the issue category from the promised action so managers can see whether delays come from evidence gathering, branch review or an approved refund awaiting completion.
Explore CaseMe in detailCapture the service issue and relevant reference, then categorise it so it reaches the right team. Use approved systems for sensitive supporting records.
Set a named owner, next action and due date. Define who reviews overdue work and how escalation should operate for this service, rather than leaving responsibility in a shared inbox.
Record what was done, the customer update and any remaining follow-up. Review repeat causes and case age so the team can improve the underlying service as well as respond to individuals.
Rental reference; issue category; responsible branch; owner; response target; approved decision; customer update
Branch manager, with finance or fleet operations assigned supporting tasks
Case age, overdue responses, deposit and damage themes, resolution time and outstanding actions by team
Start with your own baseline and compare like-for-like periods after rollout. Use confirmed activity and outcomes to assess performance; illustrative examples are not guaranteed results.

Illustrative conversation with fictional details; wording and connections are agreed before rollout.
Start with one agreed journey, its responsible team, data sources, permissions and follow-up targets. Calendar, CRM and operational-system connections, and WhatsApp or voice channels, are scoped before live use. The public demo is for exploration with fictional data.
Pro for established operators; group pricing for three or more locations.