Compare · FAQ chatbots

Price FAQs are not qualification, slots, or CRM writes

FAQ bots answer price; CoPulse agents qualify, book visits, update CRM, and hand off. A website widget that loops “2BHK or 3BHK?” without writing a Booking is a brochure. Agent Studio attaches skills and knowledge, the appointment skill holds Saturday, workflows move stages, Visit Caller confirms, the RM inherits the thread. Judge chatbots on the job, not on whether they speak.

  • Writes the Booking
  • Books the calendar
  • Handoff with context

The bot that never creates a deal

Marketing loves a bubble in the corner. Sales never sees the transcript. CoPulse web chat can qualify because visitors become leads and the conversation agent is operational: knowledge, skills, router, inbox. It is not a demo widget. Adaptive FAQ trees that “get smarter” from outcomes are not our shipped nurture. We still need operators to upload knowledge and pick templates.

Jobs, then hops

Web inquiry (OmniView hop one) → WhatsApp continuation → voice schedule → WhatsApp post-visit. There is no compare×WhatsApp nested URL.

  1. Widget on the Project Setup → Channels web.
  2. Same qualifier Not a separate FAQ brain.
  3. CRM write New enquiry Booking.
  4. Visit or handoff Appointment skill or inbox.

How CoPulse runs it

Conversation agent on web and WhatsApp. Workflows on enter. Drips if they abandon. Autonomous does not scrape anonymous visitors. SMS not a widget fallback.

Conversation agent

Agent Studio, skills, knowledge, router, inbox handoff.

Growth drips / campaigns

Clock-based. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows on pipeline stage change.

Autonomous outbound

Optional lists. Success is sends/reads — not visit booked.

Operator setup

Organization wallet. Project channels. Real Estate labels: Buyers & Tenants, Bookings.

Setup → Channels web + WhatsApp → Studio knowledge → Router → pipeline → calendars → wallet for later templates.

Midnight price question becomes Sunday 10

FAQ bot: quotes ₹1.8Cr, dead end. CoPulse: fields, plan, slot, morning Visit Caller if needed. Click-path: web inbox, Booking, appointments. website-enquiry playbook.

Stay on a FAQ chatbot if you only need after-hours brochure answers and a human reads the transcript tomorrow. Move when the widget must create Bookings and slots. No seat fee to put sales in the same inbox — wallet for AI turns and sends.

Read this page as a jobs brief, not a lawsuit. The CoPulse column is the product you can click: Setup → Channels, Library templates, Agent Studio, agent router, Agents → Workflows, autonomous list tasks (sends and reads, not appointment booked), Growth campaigns/drips, pipeline stages, appointments/calendars, omnichannel inbox, human handoff, Organization wallet. The Website FAQ chatbot widget column is category positioning. If that vendor shipped a new WhatsApp or voice module this quarter, believe their docs over our “typical” cell. We still will not invent their price. Operators implementing after a bake-off should run lead qualification, site-visit booking, and property launch on a Project — those URLs are the jobs, not nested channel clones. Adaptive nurture is not shipped. WhatsApp live catalog is Gupshup. Phone “replied” is STT. Campaign conversion is reply rate. Marketplace vs CRM suppression is a known gap — do not mix those audiences casually. Property managers should not copy token stages onto leasing. That is the honest footer for FAQ chatbots.

Vs-grid (category, not a smear)

CoPulse cells match the product. Website FAQ chatbot widget cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.

Capability CoPulse Website FAQ chatbot widget
Omnichannel inbox One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. Often the widget transcript only, emailed daily.
WhatsApp templates + 24h window In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. Operators pick templates; planners do not auto-provision session plus closed-window pairs. Usually not. A QR to WhatsApp is a different product.
Voice AI Plivo voice AI. Visit Caller confirms site visits. Phone “replied” means speech-to-text after the script — not purchase intent. Greeting trained in Agent Studio. Rare.
Pipeline / deals Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. Lead form to email. Not Bookings stages.
Drips / campaigns Growth campaigns and drips with wallet preview. Clock-based. Not adaptive nurture. Campaign conversion is still reply rate, not Interested as a first-class state. Rarely tied to a calendar hold.
Conversation agents Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. Scripted FAQ or a single LLM with no CRM write.
Workflows Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. “If they say price, send brochure.” Not stage-enter on CoPulse.
Autonomous outbound List or objective sends after plan approve. Operator picks an existing library template. Success is sends, reads, or contacted — not site visit booked. WhatsApp, email, phone only. Not list outbound with wallet preview.
Appointments / calendars Appointment skill and public calendars on the contact. Stage should match the hold. Autonomous tasks do not stop when a slot is booked. Link to Calendly maybe — not native appointment skill on the contact.
Wallet vs seats No monthly seat fees. CoPulse Unlimited: unlimited projects, agents, and channels. Organization wallet: messaging 1.10×; voice AI and LLM 1.30×; campaign cost preview before send. Widget SaaS is often a monthly site fee. We do not quote them. CoPulse: no seats, wallet for usage.
Knowledge / RAG Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. Scraped site FAQ. Not curated project PDFs in Agent Studio.
Human handoff Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. “Leave your number.” Not RM thread inheritance.

Playbooks to run, not a dump

Bake-offs fail when they stay on checkmarks. Run these three jobs on a Project.

Frequently asked questions

Including when to stay where you are.

When should we stay on a FAQ chatbot?

If the site only needs after-hours answers and sales will not work those chats as Bookings, a widget can stay. Replace it when chats must qualify, book, and hand off.

Do you list their prices?

No. Seat and conversation packs change. CoPulse publishes wallet markups on pricing: no monthly seats; messaging 1.10×; voice AI and LLM 1.30×; campaign preview before send.

Is this a complete feature matrix?

No. Named vendors ship add-ons. Our CoPulse column is the repo. Their column is category-typical. Ask them for a current demo.

Will autonomous tasks stop when a visit is booked?

No. Success is sends, reads, or contacted. Use appointment skill, drips, and Visit Caller for the visit job.

WhatsApp provider?

Live catalog is Gupshup. Do not plan an invented Meta Cloud WhatsApp hop. /channels/instagram redirects to Meta (IG/Messenger).

Can we dual-run?

Yes. Keep a CRM of record if reporting lives there. CoPulse is the omnichannel execution Project. CSV import is v1. We do not invent a native sync.

Bake off on a live Project, not a slide

Connect WhatsApp and voice, run qualification and a Saturday slot, preview the wallet on a small launch list.

Get started free