{"id":3610,"date":"2026-09-11T05:28:34","date_gmt":"2026-09-11T05:28:34","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/missed-call-crm-recovery-setup"},"modified":"2026-09-11T05:29:09","modified_gmt":"2026-09-11T05:29:09","slug":"missed-call-crm-recovery-setup","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/missed-call-crm-recovery-setup","title":{"rendered":"How to Build Missed Call Recovery CRM Integration"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI<\/em><\/p>\n<p><em>Updated: September 10, 2026<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<ul>\n<li>Missed call recovery CRM integration detects missed calls, sends instant texts, logs every interaction, creates follow-up tasks, and routes conversations to humans when needed.<\/li>\n<li>The workflow follows five core stages plus an escalation path for unresolved callers, and each stage maps directly to CRM objects.<\/li>\n<li>Duplicate prevention depends on a phone-first matching hierarchy in E.164 format, with email as a secondary match and manual review when phone matches but email does not.<\/li>\n<li>Named setup paths exist for HubSpot, Salesforce, and Zoho, with additional integrations for GoHighLevel, Pipedrive, and 50+ other tools.<\/li>\n<li>Plura AI runs the full missed call recovery loop on its own FCC-licensed carrier with stateful conversation tracking across voice, SMS, RCS, and webchat.<\/li>\n<\/ul>\n<h2>The Missed Call Recovery Flow Mapped to CRM Objects<\/h2>\n<p>Every missed call recovery workflow moves through five core stages, plus an escalation path for unresolved callers. Each stage has a defined trigger, a specific CRM write, and a designated owner. The table below maps every event to its CRM field.<\/p>\n<table>\n<thead>\n<tr>\n<th>Trigger<\/th>\n<th>CRM Object<\/th>\n<th>Field or Record Written<\/th>\n<th>Owner<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Missed call detected<\/td>\n<td>Contact or Lead<\/td>\n<td>Activity\/timeline entry with call outcome and timestamp<\/td>\n<td>System<\/td>\n<\/tr>\n<tr>\n<td>Text-back sent<\/td>\n<td>Contact<\/td>\n<td>SMS activity logged with message body and consent status<\/td>\n<td>System<\/td>\n<\/tr>\n<tr>\n<td>Reply received<\/td>\n<td>Contact<\/td>\n<td>Engagement field updated; lead score or intent flag set<\/td>\n<td>System<\/td>\n<\/tr>\n<tr>\n<td>Qualification complete<\/td>\n<td>Deal or Opportunity<\/td>\n<td>Stage updated; qualification notes appended<\/td>\n<td>Sales rep<\/td>\n<\/tr>\n<tr>\n<td>Appointment booked<\/td>\n<td>Task or Calendar event<\/td>\n<td>Task created and assigned<\/td>\n<td>Rep or dispatcher<\/td>\n<\/tr>\n<tr>\n<td>Unresolved caller<\/td>\n<td>Task<\/td>\n<td>Escalation task created with transcript link<\/td>\n<td>Human agent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The five core steps in plain terms:<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779338938448-00c130f59594.png\" alt=\"Plura SMS interface showing AI-powered business text messaging, automated customer conversations, and personalized engagement workflows.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura SMS enables personalized AI-powered text messaging with real-time customer engagement, automation, and conversational workflows.<\/em><\/figcaption><\/figure>\n<ol>\n<li><strong>Real-Time Detection.<\/strong> An inbound call goes unanswered, hits a busy signal, or reaches after-hours routing. The system writes an activity or timeline entry to the Contact or Lead record with call outcome and timestamp.<\/li>\n<li><strong>Instant Text Back.<\/strong> The missed call event fires an automated SMS. The message body and consent status log to the Contact record. <a href=\"https:\/\/www.plura.ai\/glossary\/speed-to-lead\" target=\"_blank\">Organizations deploying AI for speed to lead see connection rates increase by 3x to 5x<\/a> when response is immediate.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/li>\n<li><strong>AI Qualification.<\/strong> When the caller replies, the engagement field updates and a lead score or intent flag is set on the Contact record. This step separates casual inquiries from real opportunities.<\/li>\n<li><strong>CRM Sync.<\/strong> When qualification completes, the Deal or Opportunity stage updates and qualification notes append. The sales rep now has a clear, current record to work from.<\/li>\n<li><strong>Next Steps and Escalation.<\/strong> A booked appointment creates a Task or Calendar event assigned to the rep or dispatcher. An unresolved caller triggers an escalation task with a transcript link assigned to a human agent.<\/li>\n<\/ol>\n<p>Plura is built to execute every step in that table through its native integrations without separate middleware.<\/p>\n<h2>Phone-Number Matching and Duplicate Prevention<\/h2>\n<p>Duplicate contact creation is the most common implementation failure in missed call recovery CRM integration. An inbound number arrives, the system cannot find a match, and it creates a second record for a contact already in the CRM. A clear match hierarchy prevents that problem before any record is written.<\/p>\n<p><strong>The Matching Hierarchy:<\/strong><\/p>\n<ol>\n<li>Match by phone number first, normalized to E.164 format (for example, +12125551234).<\/li>\n<li>If no phone match, match by email.<\/li>\n<li>If no email match, create a new lead.<\/li>\n<\/ol>\n<p><strong>Three Duplicate Scenarios to Design For:<\/strong><\/p>\n<ul>\n<li><strong>Shared household numbers.<\/strong> Two contacts may share a landline. Phone match alone does not give enough confidence for an automatic merge.<\/li>\n<li><strong>Reassigned numbers.<\/strong> <a href=\"https:\/\/messageiq.io\/blogs\/avoid-costly-fines-a-guide-to-tcpa-and-can-spam-for-sms-marketing\" target=\"_blank\" rel=\"noindex nofollow\">Nearly 100,000 U.S. phone numbers are reassigned to new owners every day<\/a>, so a number on file may belong to a different person than the one who originally consented.<\/li>\n<li><strong>Leads under a different email.<\/strong> A caller may use a different email than the one on file, which creates a phone match without an email match and raises a dedupe question.<\/li>\n<\/ul>\n<p><strong>Recommended Dedupe Rule:<\/strong> Configure your CRM to flag potential duplicates when phone matches but email does not. Route those records to manual review instead of auto-merging. <a href=\"https:\/\/knowledge.hubspot.com\/records\/deduplication-of-records\" target=\"_blank\" rel=\"noindex nofollow\">HubSpot&#8217;s deduplication logic uses the Email property as its primary unique identifier for contacts<\/a>, which means phone-only matches require a custom unique value property or manual review workflow.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup> <a href=\"https:\/\/store.agents.zoho.com\/app\/agents\/duplicate-management-agent\" target=\"_blank\" rel=\"noindex nofollow\">Zoho&#8217;s Duplicate Management Agent checks records against criteria including Email, Phone, and Last Name, and adds a Duplicate tag to matching records for manual review rather than auto-merging them<\/a>.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup><\/p>\n<p>Plura uses a stateful conversation database that keys every interaction to a customer token by phone, email, or ID. The same person is recognized across voice, SMS, RCS, and webchat, and <a href=\"https:\/\/plura.ai\/integrations\" target=\"_blank\" rel=\"noindex nofollow\">CRM integration<\/a> connects that token to the contact record your team already uses.<\/p>\n<h2>CRM-Specific Setup Paths for HubSpot, Salesforce, and Zoho<\/h2>\n<p>The core flow stays consistent across platforms, but the objects and fields differ by CRM. This section outlines the named setup paths for the three CRMs operators ask about most.<\/p>\n<p><strong>Missed Call Recovery HubSpot Setup Path:<\/strong><\/p>\n<ul>\n<li><strong>Contact record:<\/strong> Phone field matched on inbound. Call outcome, SMS body, consent status, and lead status properties written. <a href=\"https:\/\/knowledge.hubspot.com\/records\/manually-log-activities-on-records\" target=\"_blank\" rel=\"noindex nofollow\">HubSpot&#8217;s default call outcome options include Busy, Connected, Left live message, Left voicemail, No answer, and Wrong number<\/a>, which map directly to missed call recovery event states.<\/li>\n<li><strong>Deal record:<\/strong> Stage updated on qualification and qualification notes appended.<\/li>\n<li><strong>Activity timeline:<\/strong> Call logged with outcome and timestamp, and SMS logged with message body.<\/li>\n<li><strong>Task object:<\/strong> Follow-up task created and assigned on appointment booking or escalation.<\/li>\n<\/ul>\n<p><strong>Missed Call Recovery Salesforce Setup Path:<\/strong><\/p>\n<ul>\n<li><strong>Lead object:<\/strong> Phone field matched on inbound, with call outcome and timestamp written to activity history.<\/li>\n<li><strong>Contact object:<\/strong> SMS body and consent status logged, and engagement field updated on reply.<\/li>\n<li><strong>Activity and Task records:<\/strong> Missed-call event mapped to activity timeline, with follow-up task created on qualification.<\/li>\n<li><strong>Opportunity object:<\/strong> Stage updated when qualification completes.<\/li>\n<\/ul>\n<p><strong>Missed Call Recovery Zoho Setup Path:<\/strong><\/p>\n<ul>\n<li><strong>Leads module:<\/strong> Phone field matched and call record created or updated on missed call. <a href=\"https:\/\/technomap.org\/blogs\/post\/zoho-crm-missed-call-follow-up-automation\" target=\"_blank\" rel=\"noindex nofollow\">Missed calls in Zoho CRM are logged via a phone system integration or Zoho PhoneBridge, which creates or updates a call record associated with a lead or contact when a call is missed<\/a>.<\/li>\n<li><strong>Contacts module:<\/strong> SMS activity logged and engagement field updated on reply.<\/li>\n<li><strong>Tasks module:<\/strong> Follow-up task created and assigned.<\/li>\n<li><strong>Activity log:<\/strong> All events written with timestamp and outcome.<\/li>\n<\/ul>\n<p>Plura also connects to GoHighLevel and Pipedrive alongside HubSpot, Salesforce, and Zoho. You can <a href=\"https:\/\/plura.ai\/integrations\" target=\"_blank\" rel=\"noindex nofollow\">connect your CRM<\/a> through Plura&#8217;s native integrations directory, which covers more than 50 tools across CRM, calendar, attribution, and payment categories.<\/p>\n<p><a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">See the setup path for your CRM in a live walkthrough<\/a>.<\/p>\n<h2>Human Handoff and Escalation for Unresolved Callers<\/h2>\n<p>Escalation functions as a designed workflow with its own CRM writes, task assignments, and transcript attachments. Treating escalation as a structured path prevents high-stakes or complex calls from stalling in automation.<\/p>\n<p><strong>What Happens With Angry, Confused, or High-Stakes Callers:<\/strong><\/p>\n<ul>\n<li><strong>Warm transfer to a U.S. agent:<\/strong> The AI recognizes the escalation trigger and routes the call to a live agent with full context. Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">live transfer<\/a> routes warm leads to U.S. agents mid-conversation.<\/li>\n<li><strong>Escalation task created in the CRM:<\/strong> A task is created with the full transcript attached and assigned to the appropriate team member.<\/li>\n<li><strong>Flag in the unified inbox:<\/strong> The conversation is flagged for human review so the team can act quickly.<\/li>\n<\/ul>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779338680098-bf2bbd201647.png\" alt=\"Plura Unified Inbox interface showing centralized AI Voice, SMS, RCS, and Webchat conversations in one omnichannel workspace.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura Unified Inbox centralizes AI Voice, SMS, RCS, and Webchat conversations into one streamlined omnichannel communication workspace.<\/em><\/figcaption><\/figure>\n<p><strong>The Guardrail Concept:<\/strong> Workflow nodes carry hard limits. When a caller&#8217;s response falls outside defined paths, the AI escalates instead of improvising. Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-voice-demo\" target=\"_blank\" rel=\"noindex nofollow\">AI voice agent<\/a> passes full transcript context to the human agent, so the handoff starts from a complete history rather than a cold open.<\/p>\n<p><a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">Review escalation task design inside your CRM in a live session<\/a>.<\/p>\n<h2>Compliance Inside the Integration: Consent, Quiet Hours, and DNC<\/h2>\n<p>Once the CRM writes are mapped, the next question is what the text-back workflow can send and when it can send it. Automated text-back workflows intersect with several regulatory frameworks. This section describes how Plura&#8217;s platform is built. It does not interpret any specific law for any specific operator. Readers should consult qualified counsel on their own obligations.<\/p>\n<p><strong>Consent Capture:<\/strong> Plura maintains timestamped and immutable consent records. <a href=\"https:\/\/peppersend.com\/tcpa-compliance-sms-guide\" target=\"_blank\" rel=\"noindex nofollow\">Under the Telephone Consumer Protection Act (TCPA), a single service-related SMS response to a consumer who initiated contact by calling a business is generally permitted without prior written consent<\/a>, and the distinction between transactional and marketing messages affects how teams design campaigns.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Plura&#8217;s consent records are audit-ready by default.<\/p>\n<p><strong>Quiet-Hours Enforcement:<\/strong> <a href=\"https:\/\/fransis.ai\/articles\/tcpa-quiet-hours-texting-times\" target=\"_blank\" rel=\"noindex nofollow\">Federal quiet-hour rules under 47 CFR 64.1200(c)(1) describe limits on telephone solicitations before 8 a.m. or after 9 p.m. in the recipient&#8217;s local time zone<\/a>.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Several states apply stricter windows. Plura enforces automated quiet-hours rules through time-zone detection inside the platform.<\/p>\n<p><strong>DNC Scrubbing:<\/strong> DNC scrubbing functions as the third compliance layer. <a href=\"https:\/\/leadcompliant.com\/articles\/sms-compliance\/tcpa-sms-marketing-compliance-rules-2025\" target=\"_blank\" rel=\"noindex nofollow\">A pre-send compliance checklist should verify a DNC scrub completed within 31 days per 47 C.F.R. \u00a7 64.1200<\/a>.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Plura enforces real-time Do Not Call (DNC) scrubbing before every dial, so the check happens before the outbound contact.<\/p>\n<p>Plura supports compliance programs related to SOC 2, HIPAA, ISO certification, GDPR, SHAKEN\/STIR caller ID verification, TCPA, and DNC.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup> Full details appear at the <a href=\"https:\/\/plura.ai\/products\/compliance\" target=\"_blank\" rel=\"noindex nofollow\">TCPA compliance<\/a> page.<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779339090994-980045ddacd2.png\" alt=\"Plura Security &amp; Compliance dashboard highlighting SOC 2, ISO, and GDPR standards with secure trust verification management.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura Security &amp; Compliance supports SOC 2, ISO, and GDPR standards with trust registration, verification management, and secure AI communications.<\/em><\/figcaption><\/figure>\n<h2>iOS Call Screening and Missed Call Detection<\/h2>\n<p>Compliance governs what the workflow sends, and detection governs whether the workflow fires at all. iOS call screening intercepts unfamiliar numbers before they ring through, which means some calls never register as missed in the phone system at all. <a href=\"https:\/\/support.apple.com\/en-us\/126076\" target=\"_blank\" rel=\"noindex nofollow\">Apple&#8217;s iOS 26 Phone app offers an Unknown Callers filter that groups missed calls and voicemails from unknown numbers into a separate list, meaning calls from unrecognized numbers may not appear in the default Unified calls view<\/a>. Any missed call recovery workflow that only monitors the main recents list will miss these calls entirely.<\/p>\n<p>Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-voice-demo\" target=\"_blank\" rel=\"noindex nofollow\">AI voice agent<\/a> communicates with the iOS 26 call-screening layer so calls present with the company&#8217;s name and the reason for the call. Screened calls convert into live pickups instead of voicemails.<\/p>\n<h2>Measuring Recovery: Tracking Missed Call to Closed Revenue Inside the CRM<\/h2>\n<p>Missed call recovery performance shows up in a clear chain of metrics that runs from missed-call volume through to closed revenue. <a href=\"https:\/\/quo.com\/blog\/small-business-callback-statistics\" target=\"_blank\" rel=\"noindex nofollow\">A Quo analysis of 16.7 million missed calls found that 69% of missed business calls do not receive a callback within 48 hours<\/a>.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> so recovery rate becomes the first number to move.<\/p>\n<p><strong>Metrics to Track:<\/strong><\/p>\n<ul>\n<li>Missed-call volume<\/li>\n<li>Text-back send rate<\/li>\n<li>Reply rate<\/li>\n<li>Appointment-set rate<\/li>\n<li>Closed revenue attributed to recovered calls<\/li>\n<\/ul>\n<p><strong>Review Cadence:<\/strong> Weekly for the first month, then monthly once baselines are established.<\/p>\n<p>Plura&#8217;s <a href=\"https:\/\/plura.ai\/calculator\" target=\"_blank\">ROI calculator<\/a> models <a href=\"https:\/\/plura.sites.aigrowthagent.co\/branded-caller-id-benefits-centers\/\" target=\"_blank\">contact-center economics in real time<\/a>, so leaders can run their own numbers through agent occupancy and AI-agent versus human-agent cost comparisons. <a href=\"https:\/\/plura.ai\/business-intelligence\" target=\"_blank\" rel=\"noindex nofollow\">Conversation intelligence<\/a> surfaces patterns across recovered conversations so the workflow improves over time.<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779338480670-5b2fbc1c92ba.png\" alt=\"Plura Conversation Intelligence dashboard displaying AI-powered call analytics, transfer tracking, and customer conversation insights.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura Conversation Intelligence gives businesses AI-powered analytics, call transfer tracking, and customer interaction insights across every conversation.<\/em><\/figcaption><\/figure>\n<h2>Conclusion: Turning Missed Calls Into CRM-Logged Opportunities<\/h2>\n<p>Missed calls without CRM integration create invisible revenue leaks. <a href=\"https:\/\/quo.com\/blog\/small-business-callback-statistics\" target=\"_blank\" rel=\"noindex nofollow\">The same Quo analysis found that 69% of missed business calls do not receive a callback within 48 hours<\/a>, which means most of those callers drift away unless a recovery workflow catches them.<\/p>\n<p>Missed call recovery CRM integration closes the gap between a missed call and a logged, followed-up opportunity. Plura runs the full loop of detection, text-back, AI qualification, CRM sync, and human handoff on its own FCC-licensed carrier with a stateful conversation database that holds context across every channel. Every event in that loop writes to the CRM objects your team already uses. Named setup paths cover HubSpot, Salesforce, and Zoho. Phone-number matching is field-level, duplicate prevention is built in, and escalation is designed as a first-class workflow.<\/p>\n<p>Compare plans and rates side by side on the <a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\">Plura pricing page<\/a>. Then run your numbers through Plura&#8217;s <a href=\"https:\/\/plura.ai\/calculator\" target=\"_blank\">ROI calculator<\/a> to evaluate your contact-center economics in real time.<\/p>\n<hr data-disclaimer-divider=\"true\">\n<div data-disclaimer-footer=\"true\">\n<p data-disclaimer-id=\"22\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"1\">1<\/sup> Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura\u2019s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.<\/p>\n<p data-disclaimer-id=\"23\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"2\">2<\/sup> This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.<\/p>\n<p data-disclaimer-id=\"24\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"3\">3<\/sup> Performance figures, customer outcomes, and industry statistics referenced in this article are drawn from cited third-party sources or Plura customer case studies. Individual results vary based on implementation, use case, industry, audience, and execution. Past or aggregate performance is not a guarantee of future results.<\/p>\n<p data-disclaimer-id=\"25\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"4\">4<\/sup> References to third-party products, services, companies, or research are made for informational and comparative purposes only. Plura AI is not affiliated with, endorsed by, or sponsored by any third party named in this article unless explicitly stated. Trademarks and product names referenced remain the property of their respective owners.<\/p>\n<p data-disclaimer-id=\"21\" data-disclaimer-type=\"fixed\">This article is provided for informational purposes only and reflects Plura AI\u2019s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.<\/p>\n<p data-disclaimer-id=\"27\" data-disclaimer-type=\"fixed\">This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.<\/p>\n<\/div>\n<section data-read-next=\"true\">\n<h2>Read Next<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-recovery-crm-integration\" target=\"_blank\">How to Integrate Missed Call Recovery with Your CRM<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-recovery-implementation-steps\" target=\"_blank\">Missed Call Recovery Implementation Steps: 2026 Setup<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-recovery\" target=\"_blank\">Missed Call Recovery Turns Unanswered Calls Into Bookings<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-recovery-checklist\" target=\"_blank\">Missed-Call Recovery Implementation Checklist<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/automatic-missed-call-recovery\" target=\"_blank\">Automatic Missed Call Recovery for High-Volume Teams<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Stop losing revenue to missed calls. Plura AI maps recovery flows to CRM objects in HubSpot, Salesforce, and Zoho. See the field-level setup guide.<\/p>\n","protected":false},"author":106,"featured_media":3609,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-3610","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-sms-automation"],"_links":{"self":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/3610","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/comments?post=3610"}],"version-history":[{"count":1,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/3610\/revisions"}],"predecessor-version":[{"id":3614,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/3610\/revisions\/3614"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/3609"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=3610"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=3610"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=3610"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}