Customer Relationship Management (CRM)Purpose
1.2 Achieve a unified, continually refreshed profile in the CRM to enable personalized ground transportation services, targeted offers, and responsive communication.
1.3 Ensure every interaction, from reservation to post-ride survey, is reflected in a single source of truth accessible by operations, customer service, and marketing.
Trigger Conditions
2.2 Customer updates contact or preference details online or via support interaction.
2.3 Transaction, ride completion, or feedback submission occurs.
2.4 Information from partner platforms (hotels, airlines) is received by API or webhook.
2.5 Marketing opt-in or out detected in communication platforms.
2.6 Duplicate customer detected during any data import or data sync task.
Platform Variants
• Feature/Setting: REST API: /services/data/vXX.X/sobjects/Contact — for creating/updating Contact records.
3.2 HubSpot
• Feature/Setting: CRM API v3 — POST/PATCH /crm/v3/objects/contacts for profile creation or updating.
3.3 Zoho CRM
• Feature/Setting: Contacts API — /crm/v2/Contacts, "upsert" function for new or updated entries.
3.4 Microsoft Dynamics 365
• Feature/Setting: "Create a new record" in the Dataverse, API endpoint /api/data/v9.1/contacts.
3.5 Freshsales
• Feature/Setting: POST/PATCH https://domain.freshsales.io/api/contacts — manage contact lifecycle.
3.6 Pipedrive
• Feature/Setting: “Persons” API, POST /persons to add and PUT /persons/{id} to update.
3.7 SugarCRM
• Feature/Setting: /rest/v11_1/Contacts for upsert operations.
3.8 Copper CRM
• Feature/Setting: People API, POST /people and PATCH /people/{id}.
3.9 Insightly
• Feature/Setting: Contacts endpoint, POST /v3.1/Contacts and PATCH /v3.1/Contacts/{id}.
3.10 Oracle CX Sales
• Feature/Setting: REST API, POST /crmRestApi/resources/latest/contacts.
3.11 Bitrix24
• Feature/Setting: CRM.contact.add & CRM.contact.update via REST endpoints.
3.12 Nimble
• Feature/Setting: Contacts API POST/PUT /contacts.
3.13 Zendesk Sell
• Feature/Setting: POST /v2/contacts and PATCH /v2/contacts/{id}.
3.14 Close CRM
• Feature/Setting: API endpoint POST /lead and PUT /lead/{lead_id}.
3.15 Intercom
• Feature/Setting: POST /contacts and PATCH /contacts/{id} API for unified customer data.
3.16 Keap (Infusionsoft)
• Feature/Setting: REST API, Contacts endpoint POST/PUT /contacts.
3.17 ActiveCampaign
• Feature/Setting: API v3, POST /contacts, PUT /contacts/{id} for real-time updates.
3.18 Monday.com
• Feature/Setting: GraphQL API, mutate column_values with customer data.
3.19 Airtable
• Feature/Setting: PATCH/POST /v0/{baseId}/{tableName} with customer field mappings.
3.20 Google Contacts
• Feature/Setting: People API, people.createContact and people.updateContact for profile sync.
3.21 ServiceNow
• Feature/Setting: Table API, POST/PATCH /api/now/table/cmdb_ci_contact for customer records.
3.22 SAP C4C (Cloud for Customer)
• Feature/Setting: REST API, POST /API_CONTACT_SRV; PATCH for updates.
3.23 Mailchimp
• Feature/Setting: POST /lists/{list_id}/members to create, PATCH for updating profile details.
3.24 Segment
• Feature/Setting: Track and Identify API – unify customer traits from multiple sources.
3.25 Slack
• Feature/Setting: Incoming Webhooks to notify team channels on profile changes.
Benefits
4.2 Accelerate issue resolution and ride scheduling by providing staff instant access to update-to-date profiles.
4.3 Enhance targeted marketing and loyalty program accuracy using real-time, comprehensive profiles.
4.4 Ensure regulatory compliance and GDPR readiness by standardizing consent and preferences.
4.5 Improve customer satisfaction through personalized communication and service.
4.6 Reduce manual data handling, lowering administrative overhead and error rates.