Lead10 by industry

Yes, by card. Send the invoice or a payment link in the chat or by email; the traveller pays and gets a receipt.

Not out of the box. Our development team can build RSVP sites and guest lists with WhatsApp invitations, and connect them to the client in Lead10.

Not with a ready-made app. Our development team connects online stores to Lead10, so orders and customers flow in automatically; on plans with API access, your own developer can use the REST API and signed webhooks. See Lead10 for online stores.

With a store connection built by our team, yes: abandoned carts trigger a WhatsApp reminder on an approved template, with a coupon code if you like.

Yes. Run each renewal as a subscription with renewal reminders, or send a WhatsApp campaign to clients whose expiry date falls in the next weeks, using a template approved by Meta.

Add a renewal date to each client, save a filter for upcoming renewals and send a weekly WhatsApp reminder campaign, with follow-up dates flagged when missed.

Not out of the box: Lead10 handles conversations, tags, files and stages. Our development team can build a job board, CV matching and client shortlists and connect them to Lead10.

Yes. Add the client's staff as users with access to their company only, and choose with roles what they can see and do. Users count towards your plan.

Yes. Support tickets with replies are kept on the client's record, so anyone on the team can see the history.

Yes. The free Android app shows the inbox, customers, visits and tasks. If your crews need job sheets, photos and signatures, our team can build a technician app connected to Lead10.

You can make it much harder. Staff without permission see masked phone numbers and emails, import and export can be switched off by role, and agents can still chat, send brochures and book viewings without the full number.

Lead10 has tasks with checklists, calendars and notes for each client. For full site and project tracking, our team can build it and connect it to Lead10.

Yes. Send an invoice for the deposit with a card payment link in the chat; the buyer pays and gets a receipt.

On the customer's record, as files next to the notes and activity. Staff without permission see masked phone numbers and emails.

Only if you allow it. Staff without permission see masked numbers and emails, and still chat, book and follow up from Lead10. Staff see only the chats assigned to them unless you give them access to all.

Yes. Clients buy packages in the portal, and memberships run as subscriptions charged to their card every month.

Map your stages, such as Trial booked, Trial attended and Member, and Lead10 reports each one to Meta and Google Ads as a conversion when a coach changes the stage.

Yes. Set up stages such as Counselling, Documents pending, Offer received and Visa, and fields for destination, university and intake. Lead10 doesn't connect to university application portals out of the box; counsellors track each application in Lead10, and our development team can build an application tracker or student portal around your process.

Not out of the box. Our team can connect your POS so visits and spend appear on each guest in Lead10.

With a PMS connection built by our team, yes: messages on approved templates are triggered by arrivals and checkouts. Without it, you can send campaigns to saved filters of guests.

Yes, for people who message from your click-to-WhatsApp or click-to-Messenger ads: each ad can send its own itinerary, photos and video at once. Consultants can also send saved itineraries as quick replies by typing /.

Keep vendors as contacts and their deadlines as tasks with checklists. For quotes and contracts from vendors, our team can build a vendor portal.

Yes, with a card payment link. Send the invoice or payment link in the chat; the customer pays by card and gets a receipt.

Yes, with a store connection: confirmed, shipped and out-for-delivery messages, and cash-on-delivery confirmations that update the order.

No, not out of the box; applications are still submitted on the official portals. Our development team can build tools around your process, such as document portals and expiry trackers, and connect them to Lead10.

Staff without permission see masked numbers and emails and only their own chats; every workspace has a separate database, privacy tools record consent and erasure requests, and two-step sign-in is available for every user. Lead10 doesn't hold insurance-sector certifications.

Yes. Each contract runs as a subscription that invoices in advance, with renewal reminders and your own chase rules.

You can create, monitor and optimise Google and Meta campaigns from Lead10. You still need the Google Ads and Meta ad accounts, and ad spend is billed by Google and Meta, not by Lead10.

Yes. On plans with API access, use the REST API and signed webhooks, or let our development team build and maintain the integration for you.

Yes. Each contract runs as a subscription billed monthly, quarterly or yearly, with renewal reminders and optional automatic card payments.

Yes. Lead10 connects to Meta's official WhatsApp Cloud API directly, with no reseller in between. Message templates are created in Lead10, submitted to Meta for approval and synced back.

Only if you allow it. By default they see the conversations assigned to them, and roles decide whose records each person can see.

Every lead records the ad it came from, and when a salesperson marks a car sold, Lead10 reports the sale to Meta and Google Ads as a conversion.

Yes. Add the company as a client with several contacts, and send its quotes and invoices, including monthly lease invoices.

Yes. Patients sign in to the portal with an email code or a WhatsApp message and buy the packages you list. Monthly memberships can run as subscriptions, charged to their card automatically.

Yes. Notes and photos go on the client's timeline, so any stylist can see what was used last time.

Yes. Give each creator or member a coupon code; anyone who sends it on WhatsApp, Instagram or Messenger gets an automatic reply with the offer.

Only if you allow it. By default they see the conversations assigned to them, and roles decide whether someone sees their own records or everyone's, by campus if you have several.

Yes. Send a WhatsApp campaign with an approved template and a coupon code; guests who send the code back get an automatic reply confirming the offer.

Send proposals with rooms, meeting space and food as a PDF the client signs online, then invoice the deposit with a card payment link.

Only if you allow it. By default they see the conversations assigned to them, and staff without permission see masked phone numbers and emails.

Every enquiry records the ad it came from, and booked events are reported to Meta and Google Ads as conversions with their value.

Yes. Each creator gets a coupon code and a passwordless portal. Customers who send the code on WhatsApp, Instagram or Messenger get an automatic reply, and commission is worked out on the plan you choose.

Yes. Build customer lists from saved filters, push them to Meta and Google on a schedule, and create Meta lookalikes.

You can make it much harder. Staff without permission see masked numbers and emails, see only their own chats, and export can be switched off by role.

Yes. Photos and PDFs sent in the chat stay with the conversation, and brokers attach them to the client's record.

Yes. Send a campaign to candidates tagged for a role, using a template approved by Meta. Anyone who replies STOP is never messaged again.

Yes. Each retainer runs as a subscription that invoices in advance, sends renewal reminders and follows your chase and cancel rules. Card payments can be collected automatically, with the retainer paused if a payment fails.

Yes. Every lead has a value and an owner, and dashboards show the funnel, pipeline and sources for any period.

Yes. Set up a monthly WhatsApp campaign to a saved filter of customers whose last service date has passed, using a template approved by Meta.