Skip to content
Volāre Documentation

Customers

The Customers navigation group holds the three records that describe the people Volāre deals with: Leads (raw enquiries from the website), Clients (the account that books and pays), and Passengers (the individuals who actually travel, with their travel documents). Leads, Clients, and Passengers are each synced one-way to Pipedrive CRM so the sales team works from a single source (see Pipedrive CRM Sync).

Who Uses This

Section titled “Who Uses This”
  • Sales / customer-service agents following up on enquiries and managing client accounts.
  • Operations, for passenger travel documents ahead of departure.

What Each Item Manages

Section titled “What Each Item Manages”

Leads

Section titled “Leads”

Read-only in Arkana. Leads are created only by the public contact form via the Leads API — agents can view them but not create or edit them. Each lead captures name/email/phone, the destinations the visitor selected (regions and/or countries), a preferred call time, and the consent audit trail (consent_given_at, privacy-policy version, and IP) recorded server-side at submission for GDPR compliance.

On capture, a lead is pushed to Pipedrive’s Leads Inbox through a queued, retryable job. The only source today is the homepage contact form.

Clients

Section titled “Clients”

Full account records — the party that books and pays. Managed here: contact details, an Active status (inactive clients cannot make new bookings), billing address, CRM/preferences (preferred language and currency, lead source, sales rep), and internal notes. The table surfaces business analytics: lifetime value (LTV), total bookings, last booking date, and lead-source breakdown, with filters for recent and high-value clients.

A client is linked to its bookings, payments, and payment methods, and to passengers through a many-to-many relationship (with pivot data such as relationship type and primary-contact flag). A client with associated bookings cannot be deleted.

Passengers

Section titled “Passengers”

The individuals who travel. The critical section is Travel Documents: legal name as on passport, passport number, issuing country, expiry (must be valid at least 6 months out — the table flags passports expiring within 6 months), nationality and residence countries, and visa requirements. Also managed: basic details (name, date of birth which drives the adult/child/infant age category, gender), contact info, travel preferences and accessibility/dietary/medical needs, DOCA/APIS address data, emergency contact, and a documents-complete flag.

A passenger links to the clients they travel with and to their flight bookings (with per-booking pivot state such as lead-passenger and document-approval flags).

Key Rules

Section titled “Key Rules”
  • Leads are read-only in the panel and only ever created via the contact-form API.
  • Consent is captured server-side (timestamp, policy version, IP) — never trusted from the client.
  • Clients with bookings can’t be deleted; inactive clients can’t start new bookings.
  • Passport expiry must be at least 6 months out; near-expiry passports are flagged.
  • All three models are activity-logged and synced one-way to Pipedrive.
Section titled “Related”
  • Leads API — the public capture endpoint and consent handling
  • Pipedrive CRM Sync — how leads/clients/passengers reach the CRM
  • Source: backend/app/Filament/Resources/ClientResource.php, backend/app/Filament/Resources/Leads/, backend/app/Filament/Resources/PassengerResource.php