CoreBeginner
7 min read
Updated 30 April 2025

Leads & CRM Pipeline

The QuintaGo CRM is the central hub for all your leads. Every enquiry — whether it arrives via WhatsApp, your website form, or manual entry — flows into the same pipeline where your team can track, qualify, and close it.

Pipeline stages

The default pipeline has five stages. You can rename, reorder, or add custom stages in Settings → Pipeline:

  • New enquiry — lead has just arrived, not yet contacted
  • Contacted — first contact made, waiting on response
  • Visit booked — a site visit has been scheduled
  • Proposal sent — proposal delivered, awaiting decision
  • Signed — contract signed, booking confirmed

Lead profile

Each lead has a dedicated profile page containing:

  • Contact details (name, email, phone)
  • Event details (date, guest count, type, budget)
  • Full conversation history (WhatsApp + email)
  • Timeline of all actions (stage changes, proposals, notes)
  • Linked proposals and their status
  • Custom fields specific to your venue

Importing leads

Bring in leads from an existing spreadsheet or CRM via CSV import at Leads → Import.

# Required columns
name, email

# Optional but recommended
phone, event_date, guests, stage, notes, tags

# Example row
"Ana Pereira","ana@example.com","+351912345678","2025-10-15","120","contacted","Budget ~10k","vip,autumn"

Duplicate detection runs on email address and phone number. Existing leads are updated rather than duplicated.

Lead scoring

QuintaGo automatically scores leads from 1–100 based on signals including response rate, event date proximity, guest count, and engagement level. Scores appear as a colour-coded indicator on each lead card and can be used to filter the pipeline.

Tags and segments

Use tags to label leads with custom categories such as vip, high-budget, or 2025-autumn. Saved segments let you filter by multiple criteria and use the result as a broadcast audience.

Best practices

  • Respond to new leads within 5 minutes — use the AI Concierge for instant replies
  • Set a follow-up task on every lead that enters the Contacted stage
  • Use custom fields to track venue-specific data (indoor/outdoor preference, catering choice)
  • Archive lost leads with a reason to improve pipeline analytics
Tags:leadscrmpipeline

Was this article helpful?