CRM CRM Mobile and Integration 1 — Questions and Answers
Question 1: What is 'mobile CRM' and why is it important for sales teams?
- A CRM designed only for smartphone companies
- A CRM accessible via mobile devices enabling sales reps to manage customer relationships in the field (Correct answer)
- A CRM for managing mobile advertising campaigns
- A lightweight CRM for small teams
Correct answer: A CRM accessible via mobile devices enabling sales reps to manage customer relationships in the field
Mobile CRM provides access to customer data, deal management, and sales tools on smartphones and tablets for field sales reps.
Mobile CRM extends CRM functionality to smartphones and tablets, enabling sales reps to access customer information, update deals, log calls, and view schedules while in the field or between meetings. Key mobile CRM capabilities include: offline mode (sync when reconnected), voice-to-text notes, GPS check-in for customer visits, business card scanning, push notifications for urgent updates, and one-tap calling with automatic call logging. Major CRMs (Salesforce, HubSpot, Dynamics 365) offer native mobile apps. Mobile CRM adoption improves data currency as reps log information immediately after interactions rather than waiting until they return to the office.
Question 2: What is a CRM 'API integration' with third-party tools?
- A manual data export process
- A programmatic connection enabling automatic data exchange between the CRM and external applications (Correct answer)
- A user interface plugin for the CRM
- A security authentication protocol
Correct answer: A programmatic connection enabling automatic data exchange between the CRM and external applications
CRM API integrations create programmatic connections enabling real-time or scheduled automatic data exchange with external tools like email, accounting, or marketing software.
CRM API integrations use REST APIs, webhooks, or middleware to connect the CRM with other business software. Common integrations include: Email platforms (Outlook, Gmail) for logging correspondence, Marketing automation (Marketo, Pardot) for lead sync, ERP systems (SAP, NetSuite) for order and financial data, Communication tools (Slack, Teams) for notifications, E-commerce platforms (Shopify, Magento) for purchase history, and accounting software (QuickBooks, Xero) for invoice status. API integrations eliminate manual data entry between systems and ensure all teams have current information. Integration platforms like Zapier, MuleSoft, and Workato simplify creating connections without custom code.
Question 3: What is 'native integration' versus 'third-party integration' in CRM?
- Native integrations are free; third-party integrations cost extra
- Native integrations are built and maintained by the CRM vendor; third-party integrations are built by external developers (Correct answer)
- Native integrations are for mobile; third-party are for desktop
- Native integrations use data from the same country; third-party use international data
Correct answer: Native integrations are built and maintained by the CRM vendor; third-party integrations are built by external developers
Native integrations are officially developed by the CRM vendor for specific tools; third-party integrations are built by external developers or middleware platforms.
Native CRM integrations are officially built and maintained by the CRM vendor for specific platforms — for example, Salesforce's native Gmail integration or HubSpot's native Slack integration. They typically require minimal setup, are officially supported, and update automatically with product releases. Third-party integrations are built by external developers using the CRM's API — available on marketplaces like Salesforce AppExchange or HubSpot Marketplace. Integration middleware (iPaaS) platforms like Zapier, Make (Integromat), MuleSoft, and Workato build and maintain thousands of connectors. Native integrations offer deeper functionality; third-party solutions offer broader coverage.
Question 4: What is 'webhook' in CRM integration contexts?
- A physical connection between CRM servers
- An automated HTTP notification sent by one system to another when a specific event occurs (Correct answer)
- A type of CRM form that embeds in websites
- A web scraping tool for CRM data
Correct answer: An automated HTTP notification sent by one system to another when a specific event occurs
A webhook is an event-driven HTTP notification sent by a CRM to an external URL when a specific trigger event occurs, enabling real-time integration.
Webhooks are a lightweight integration mechanism where a CRM automatically sends an HTTP POST request to a specified URL whenever a defined event occurs. For example: when a deal is won in Salesforce → webhook fires → triggers an order creation workflow in NetSuite; when a new contact is created in HubSpot → webhook fires → adds contact to an external loyalty database. Unlike polling (periodically asking 'did anything change?'), webhooks push data immediately when events occur, enabling real-time integrations. Most major CRMs support outbound webhooks, and integration platforms like Zapier receive webhooks and route them to downstream actions.
Question 5: What does 'CRM offline mode' provide for mobile users?
- Access to CRM while disconnected from the internet, with syncing when reconnected (Correct answer)
- A CRM that doesn't require internet at all
- A read-only view of CRM data for offline review
- An offline backup of all CRM data
Correct answer: Access to CRM while disconnected from the internet, with syncing when reconnected
CRM offline mode allows sales reps to view and edit data without internet connection, then automatically syncs changes when connectivity is restored.
CRM offline mode is critical for field sales reps who may be in areas with poor connectivity — customer manufacturing facilities, rural accounts, or during flights. Offline capabilities allow users to: view contact and account information, update opportunity stages and notes, log calls and meetings, and check schedules. When connectivity is restored, the mobile app syncs all changes with the cloud CRM, handling conflict resolution if the same record was updated by multiple users offline. Salesforce Mobile and Microsoft Dynamics Field Service are examples of CRMs with robust offline capabilities.
Question 6: What is 'single sign-on' (SSO) in CRM deployment?
- A CRM accessible to only one user at a time
- Authentication allowing users to log in once and access the CRM and all connected apps without re-entering credentials (Correct answer)
- A simplified one-step CRM login process
- Logging into the CRM from a single device only
Correct answer: Authentication allowing users to log in once and access the CRM and all connected apps without re-entering credentials
SSO allows users to authenticate once through a central identity provider and gain access to the CRM and all connected systems without separate logins.
Single Sign-On (SSO) in CRM uses identity providers (IdP) like Okta, Azure Active Directory, or Google Workspace to centralize authentication. Users log in to the company's identity provider once and access the CRM (and all connected applications) without separate logins. SSO benefits include: improved security (fewer passwords = fewer attack vectors), better user experience (one login for everything), centralized access control (revoke access to all apps simultaneously when an employee leaves), audit trail for compliance, and ability to enforce MFA in one place. Major CRMs support SAML 2.0 and OAuth 2.0 SSO standards.
CRM CRM Mobile and Integration 1
What is 'mobile CRM' and why is it important for sales teams?