There is a queue at the counter, and a longer one waiting on WhatsApp.

Rocketly is a CRM layer for pharmacy customer communication and requests: stock enquiries, dermocosmetic consultations and corporate orders from connected channels attach to a customer record, preparation and delivery stages are tracked, reminder routines are configured and the process becomes reportable. It does not replace your pharmacy management software, medicine tracking system or prescription reimbursement flow; it works alongside them as the communication and follow-up layer.

No. Stock and sales records stay in your pharmacy management software, and Rocketly does not read till data from it on its own. A customer asking "do you have this product?" opens a tracked request, gets assigned to a member of staff and stays visible until it closes. Staff check availability in the pharmacy software and answer, and that answer is written into the same conversation. Over time this turns unmet product enquiries into reportable information.

Yes. Connected sources such as WhatsApp Business, a personal WhatsApp line, Instagram DM and story replies, Facebook Messenger, Telegram, email, SMS and the web chat widget appear in the same inbox. Rocketly supports 12 channel types in total; which ones you can open depends on your account configuration and plan. At shift handover the team sees the same history.

No. AI produces assisting output only: conversation summaries and reply drafts based on your knowledge base. Every question about a medicine, dose, substitute or interaction is routed to the pharmacist; AI gives no medical direction and does not interpret a prescription. It is recommended that your knowledge base holds only non-clinical content such as opening hours, service scope and process steps. Final review of customer-facing text and sending authorization stay with your team.

Workflow Builder ships with 55 templates and offers 46 trigger types. For customers tagged by regular-use group, you plan a reminder as the refill window approaches: a trigger, a condition (contact consent exists) and an action (message draft, task or notification). The pharmacist approves the wording and the send, and a neutral reminder that names no medicine is often preferred.

Access is role-based: you define which records, conversations and reports assistants, technicians and pharmacists can see. Prescription-related threads can be closed to a narrow role. The infrastructure is built to operate in line with data protection requirements and activity history is retained. Deciding which health data never enters this layer at all remains with your pharmacy, and working with the minimum necessary data is the usual choice.

Yes. Customer segmentation separates corporate records such as care homes, clinics and companies from walk-in neighbourhood customers, and you define different process stages and reminder intervals for each. Corporate requests document the item list through the quote and invoice modules, while neighbourhood customers lean on dermocosmetic advice and refill reminders. Reports show the two groups apart.

Yes. Bulk import runs from CSV, Excel, VCF and Google Sheets, mapping name, phone, email, segment and custom fields. Checking the mapping with a sample file before the full import is recommended. You decide which fields travel: contact and request information usually moves, while health data such as prescription detail is commonly kept out of this layer entirely.

Yes. There is a permanently free plan, no credit card is requested and there is no trial-period concept. AI, advanced workflows and some channel connections sit in paid plans. The pricing page shows which feature belongs to which plan, and you can start with the WhatsApp line alone, then add channels and flows as the pharmacy settles into the routine.