{"id":1056,"date":"2026-07-18T05:19:21","date_gmt":"2026-07-18T05:19:21","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/tcpa-compliant-crm-sms"},"modified":"2026-07-18T05:19:21","modified_gmt":"2026-07-18T05:19:21","slug":"tcpa-compliant-crm-sms","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/tcpa-compliant-crm-sms","title":{"rendered":"TCPA-Compliant CRM SMS: What Your Platform Must Do"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways for TCPA-Compliant CRM SMS<\/h2>\n<ul>\n<li>TCPA-compliant CRM SMS keeps consent records, instant STOP handling, real-time DNC scrubbing, and audit-ready logs inside your CRM workflow.<\/li>\n<li>Separate compliance tools outside the CRM create risk through delayed opt-out updates and incomplete audit trails.<\/li>\n<li>Plura AI integrates with Salesforce, HubSpot, and GoHighLevel to run consent checks, DNC scrubbing, and quiet-hours rules at the carrier level.<\/li>\n<li>A six-field consent model plus a pre-send decision tree checks every message against federal and state rules before it is queued.<\/li>\n<li>Learn how Plura AI can help you run TCPA-compliant CRM SMS at scale: <a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">start here<\/a>.<\/li>\n<\/ul>\n<h2>What TCPA-Compliant CRM SMS Covers in Practice<\/h2>\n<p>TCPA-compliant CRM SMS checks every outbound text against documented prior express written consent, federal and state DNC registries, 10DLC registration, and recipient time-zone quiet hours before the carrier sends the message. Consent records, opt-out processing, and delivery logs live in the CRM so operators can export audit-ready reports on demand. The Telephone Consumer Protection Act (47 U.S.C. \u00a7 227) and FCC regulations set a federal baseline, while state mini-TCPA statutes in Florida, Oklahoma, Texas, and others add further requirements.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Operators should consult qualified counsel for obligations tied to their states, channels, and use cases.<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779337911454-8c3a9645d906.png\" alt=\"Screenshot of Plura\u2019s fully compliant AI communications platform showing business registration and phone number provisioning workflows for AI Voice, SMS, RCS, and Webchat communication automation.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura\u2019s FCC-licensed AI communications platform simplifies compliant business registration and phone number provisioning for AI Voice, SMS, RCS, and Webchat workflows.<\/em><\/figcaption><\/figure>\n<h2>1. Why Compliance Outside the CRM Increases Risk<\/h2>\n<p>High-volume teams lose control when compliance sits outside the CRM. Consent records live in one tool, STOP commands land in another, and DNC checks run in a third system that may not sync in real time. This fragmentation produces inconsistent suppression logic, slow opt-out updates, and audit trails that are difficult to assemble when a regulator or plaintiff requests them.<\/p>\n<p>The financial exposure is material. TCPA lawsuits rose nearly 27% in early 2026 compared to 2025, after a <a href=\"https:\/\/natlawreview.com\/article\/midyear-litigation-report-tcpa-class-actions-staggering-952-2024-previously-highest\" target=\"_blank\" rel=\"noindex nofollow\">95% surge in TCPA class actions during 2025<\/a>. The average TCPA class action settlement in 2018 was $6.6 million, and statutory damages range from $500 to $1,500 per non-compliant message with no aggregate cap.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> A campaign of 100,000 messages without proper consent documentation can create exposure exceeding $150 million in a class action. This level of risk calls for a different compliance architecture that treats the CRM as the control center.<\/p>\n<p>Plura moves enforcement inside the CRM workflow at the carrier level, so consent status, DNC scrub results, and opt-out events write back to the contact record before any message is queued. The implementation process below shows how this architecture works in daily operations, and teams that need to align cost and throughput can <a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\">compare plans and rates side by side at plura.ai\/pricing<\/a>.<\/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>2. Who Should Use This Guide and What You Need Ready<\/h2>\n<p>This guide serves contact-center leaders, sales-operations directors, and compliance officers handling at least 500 daily customer interactions via SMS. Typical use cases include lead follow-up, appointment reminders, and customer-service messaging across Salesforce, HubSpot, and GoHighLevel.<\/p>\n<p>Have these elements in place before implementation:<\/p>\n<ul>\n<li>An existing CRM with contact records that store phone numbers in E.164 format<\/li>\n<li>A documented consent process that captures prior express written consent, including disclosure text, timestamp, and capture channel<\/li>\n<li>A legal entity name and EIN ready for 10DLC brand registration through The Campaign Registry (TCR)<\/li>\n<li>Qualified legal counsel engaged to review TCPA and state-level obligations for your specific use cases<\/li>\n<li>A suppression list of previously opted-out contacts to import before any campaign runs<\/li>\n<\/ul>\n<h2>3. Six-Step Implementation Process for CRM-Based TCPA Controls<\/h2>\n<h3>Step 1: Map Six Consent Fields on Every CRM Contact<\/h3>\n<p>Standardize six discrete consent fields on every contact record. <a href=\"https:\/\/agxntsix.ai\/guides\/tcpa-consent-mapping-dnc-auditable-records-crm\" target=\"_blank\" rel=\"noindex nofollow\">Enterprise CRMs should treat any record missing these fields as non-sendable by default<\/a>:<\/p>\n<ol>\n<li><strong>Consent status<\/strong> &#8211; active, revoked, disputed, or unknown<\/li>\n<li><strong>Consent source<\/strong> &#8211; web form, inbound call, or SMS keyword<\/li>\n<li><strong>Timestamp with time zone<\/strong> &#8211; UTC format, ISO 8601<\/li>\n<li><strong>Channel scope<\/strong> &#8211; voice, SMS, or email, since consent for one channel does not cover others<\/li>\n<li><strong>Disclosure version<\/strong> &#8211; the exact text the consumer saw at opt-in<\/li>\n<li><strong>Certificate URL<\/strong> &#8211; TrustedForm or equivalent proof-of-consent record<\/li>\n<\/ol>\n<p>The TSR requires sellers and telemarketers to retain consent records for 5 years, and many operators align retention with that window to cover the statute of limitations.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> When capturing that consent, pre-checked boxes do not satisfy current TCPA standards, so the consumer must take an affirmative action such as clicking an unchecked box.<\/p>\n<h3>Step 2: Connect Plura AI Through the Integrations Layer<\/h3>\n<p>Connect Plura to your CRM through <a href=\"https:\/\/plura.ai\/integrations\" target=\"_blank\" rel=\"noindex nofollow\">plura.ai\/integrations<\/a>. Native integrations cover Salesforce, HubSpot, and GoHighLevel, and Zapier and Make support additional workflow automation. The integration writes consent status, opt-out events, DNC scrub results, and message delivery logs back to the contact record in real time, which keeps the CRM as the single source of truth for compliance documentation.<\/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<p><a href=\"https:\/\/sakari.io\/blog\/enterprise-text-messaging-solutions-complete-guide-for-business-communication\" target=\"_blank\" rel=\"noindex nofollow\">Platforms should support API connectivity tested via sandbox access before commitment, with bidirectional contact updates and automatic message-history logging inside CRMs such as Salesforce and HubSpot<\/a>. This connectivity ensures that compliance events do not sit in a separate, unsynced system.<\/p>\n<h3>Step 3: Register 10DLC Campaigns at the Carrier Layer<\/h3>\n<p>10DLC registration for application-to-person messaging over 10-digit long-code numbers runs through The Campaign Registry in two steps: brand registration and campaign registration. <a href=\"https:\/\/idtexpress.com\/blog\/10dlc-registration-guide\" target=\"_blank\" rel=\"noindex nofollow\">Brand registration typically completes within a few hours to 2 business days, while campaign registration can take 1 to 4 weeks depending on CSP relationships<\/a>.<\/p>\n<p>Plura\u2019s carrier layer manages TCR submission and assigns numbers to approved campaigns. <a href=\"https:\/\/getvero.com\/resources\/the-ultimate-guide-to-sms-marketing-in-2026\" target=\"_blank\" rel=\"noindex nofollow\">Unregistered campaigns often see delivery rates fall to 60 to 70%<\/a>, and since February 2025, the major carriers block unregistered A2P traffic from 10-digit numbers entirely. Register distinct campaigns for each use case such as marketing, transactional, and customer care, because a mismatch between the registered use case and actual traffic can trigger carrier filtering.<\/p>\n<h3>Step 4: Turn On Real-Time DNC Scrubbing and SHAKEN\/STIR<\/h3>\n<p>Plura integrates with The Blacklist Alliance\u2019s TCPA Litigation Firewall for <a href=\"https:\/\/www.plura.ai\/compare\/plura-ai-vs-vapi\" target=\"_blank\">real-time DNC scrubbing and litigation protection<\/a>.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup> Every outbound contact is checked against federal and state DNC registries before the message is queued. <a href=\"https:\/\/lineshield.theidudes.com\/blog\/dnc-scrubbing-compliance-insurance-dialers\" target=\"_blank\" rel=\"noindex nofollow\">The FTC\u2019s Telemarketing Sales Rule calls for calling lists to be scrubbed against the National DNC Registry at least every 31 days<\/a>, and many operators use real-time scrubbing via compliance APIs as an operational standard. Each scrub decision is logged with timestamp, lists checked, and result to support an audit-ready defense.<\/p>\n<p>SHAKEN\/STIR caller-ID authentication runs on every outbound contact through Plura\u2019s FCC-licensed carrier, which helps destination carriers verify legitimate origination.<\/p>\n<h3>Step 5: Configure STOP Handling and Quiet Hours by Time Zone<\/h3>\n<p><a href=\"https:\/\/beancount.io\/blog\/2026\/06\/04\/tcpa-a2p-10dlc-sms-marketing-compliance-2026-small-business-text-program-the-campaign-registry-consent-stop-help-keyword-state-mini-tcpa-florida-ftsa-texas-sb140-guide\" target=\"_blank\" rel=\"noindex nofollow\">TCPA and CTIA guidelines call for SMS platforms to recognize and honor STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPT OUT, OPTOUT, and OPT-OUT immediately<\/a>, with the opted-out number suppressed across every campaign for that brand. Plura processes these keywords at the carrier level and writes the opt-out event back to the CRM contact record in real time, updates the consent status field, and cancels active sequences.<\/p>\n<p>Federal TCPA quiet hours prohibit marketing SMS before 8 a.m. or after 9 p.m. in the recipient\u2019s local time zone. <a href=\"https:\/\/idtexpress.com\/hi\/blog\/tcpa-compliance-for-sms-in-2026-the-complete-guide-for-us-businesses\" target=\"_blank\" rel=\"noindex nofollow\">Florida, Oklahoma, and Washington apply an 8 a.m. to 8 p.m. window, and Texas applies 9 a.m. to 9 p.m. Monday through Saturday and 12 p.m. to 9 p.m. Sunday<\/a>. Plura enforces quiet hours by the contact\u2019s local time zone automatically and applies the most restrictive applicable rule for each recipient location.<\/p>\n<h3>Step 6: Enable Compliance Logging and One-Click Audit Exports<\/h3>\n<p>Plura\u2019s compliance engine supports logging for SOC 2, HIPAA, ISO certification, GDPR, TCPA, and DNC-related workflows across every SMS interaction.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup> <a href=\"https:\/\/www.plura.ai\/guides\/ai-communications-strategy\" target=\"_blank\">Plura AI\u2019s compliance framework includes SOC 2-compliant infrastructure, TCPA and SHAKEN\/STIR enforcement, integration with Blacklist Alliance for DNC screening, and Number Verifier for caller ID reputation<\/a>.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup> The compliance dashboard exports audit-ready reports in one click for legal review, carrier requests, or regulatory inquiries. Customers remain responsible for their own compliance obligations, and Plura provides the infrastructure and logging layer that supports those programs.<\/p>\n<h2>4. How the Six-Field Consent Model Drives the Decision Tree<\/h2>\n<p>The six-field consent model in Step 1 feeds a pre-send decision tree that runs before any message is queued:<\/p>\n<ol>\n<li>Confirm that consent status is \u201cactive\u201d for the SMS channel scope. If not, block the send.<\/li>\n<li>Check whether the contact appears on federal or state DNC registries. If listed, block the send.<\/li>\n<li>Verify that the sending number is registered to an approved 10DLC campaign that matches this use case. If not, block the send.<\/li>\n<li>Confirm that the current time falls within permitted hours for the contact\u2019s local time zone. If not, queue the message for the next allowed window.<\/li>\n<li>Check the consent timestamp against the Reassigned Numbers Database when consent is more than 30 days old. If not verified, query the RND before sending.<\/li>\n<li>When all gates clear, queue the message and log the send event to the CRM contact record.<\/li>\n<\/ol>\n<p><a href=\"https:\/\/agxntsix.ai\/guides\/tcpa-consent-mapping-dnc-auditable-records-crm\" target=\"_blank\" rel=\"noindex nofollow\">Direct CRM-to-DNC compliance API integration enables real-time list scrubbing before each outbound contact and can yield a 9% increase in operational contact efficiency by removing contacts that would trigger violations<\/a>.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<h2>5. Common Implementation Issues and How to Address Them<\/h2>\n<p>The following issues appear most often during rollout:<\/p>\n<ul>\n<li><strong>Missing consent timestamps:<\/strong> Contacts imported from legacy lists often lack the exact disclosure version and timestamp required for a defensible audit trail. Treat these records as non-sendable, flag them clearly in the CRM, and run a re-consent campaign before including them in any outbound sequence.<\/li>\n<li><strong>Delayed STOP propagation:<\/strong> When opt-out events are processed by a bolt-on tool instead of writing directly to the CRM, suppression can lag across automated triggers. Plura\u2019s carrier-level integration writes opt-out status to the CRM contact record in real time and blocks all subsequent automated sends immediately.<\/li>\n<li><strong>Time-zone mismatches:<\/strong> Sending platforms that use the sender\u2019s time zone instead of the recipient\u2019s time zone for quiet-hours enforcement create exposure in multi-state campaigns. Plura enforces quiet hours by the contact\u2019s local time zone at the carrier layer.<\/li>\n<li><strong>10DLC trust-score rejections:<\/strong> <a href=\"https:\/\/idtexpress.com\/blog\/10dlc-registration-guide\" target=\"_blank\" rel=\"noindex nofollow\">TCR assigns a Trust Score based on EIN age, exact name-EIN match, Dun and Bradstreet presence, and compliance history<\/a>. Scores below 49 limit throughput significantly. Secondary vetting via Aegis Mobile, which typically costs $40 to $60, can raise scores into the 75-plus range that unlocks higher daily message limits. Plura\u2019s carrier layer guides this process during onboarding.<\/li>\n<li><strong>Reassigned number exposure:<\/strong> Millions of telephone numbers are reassigned each year in the United States, and consent attaches to the individual rather than the phone number. Query the RND before sending to any contact where consent was obtained more than 30 days earlier.<\/li>\n<\/ul>\n<h2>6. Metrics That Show Whether the Program Is Working<\/h2>\n<p>Track these metrics to evaluate the health of a TCPA-compliant CRM SMS deployment:<\/p>\n<ul>\n<li><strong>Consent-record completeness rate:<\/strong> Percentage of sendable contacts with all six consent fields populated. Aim for full coverage before campaigns launch.<\/li>\n<li><strong>Opt-out processing time:<\/strong> Time from STOP receipt to suppression across all systems. Real-time processing should be the operational standard.<\/li>\n<li><strong>DNC scrub hit rate:<\/strong> Percentage of contacts blocked by federal or state DNC scrubbing before send. A rising hit rate signals list hygiene issues that need attention.<\/li>\n<li><strong>Quiet-hours violation count:<\/strong> This should remain at zero. Any non-zero count indicates a time-zone enforcement gap in the automation layer.<\/li>\n<li><strong>Audit-export generation time:<\/strong> Time required to produce a complete consent and delivery log for a specific contact or campaign. One-click export is the target state.<\/li>\n<li><strong>10DLC delivery rate:<\/strong> Registered campaigns on Plura\u2019s carrier layer should maintain delivery rates well above the 60 to 70% floor seen with unregistered traffic.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/plura.ai\/calculator\" target=\"_blank\">Run your numbers through Plura\u2019s ROI calculator to estimate cost savings in real time at plura.ai\/calculator.<\/a><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Which CRM systems connect with Plura AI for TCPA-focused SMS?<\/h3>\n<p>Plura integrates natively with Salesforce, HubSpot, and GoHighLevel, and supports additional CRM connections through Zapier and Make.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup> The integration layer writes consent status, opt-out events, DNC scrub results, and message delivery logs back to the contact record in real time. This approach keeps the CRM as the single source of truth for compliance documentation instead of forcing operators to reconcile records across multiple bolt-on tools. The full integration directory is available at plura.ai\/integrations.<\/p>\n<h3>How does Plura process STOP and UNSUBSCRIBE commands?<\/h3>\n<p>Plura processes STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPT OUT, OPTOUT, and OPT-OUT at the carrier level as soon as the keyword is received. The opt-out event writes back to the CRM contact record in real time, the consent status field updates to \u201crevoked,\u201d and all active automated sequences for that contact are canceled. A single non-promotional confirmation message is sent to the contact, and no further marketing messages are queued. This suppression applies across every campaign associated with that brand.<\/p>\n<h3>What is 10DLC registration and why does it matter for CRM SMS?<\/h3>\n<p>10DLC refers to 10-digit long codes used for application-to-person business messaging in the United States. The Campaign Registry manages brand and campaign registration, and carriers use that data to confirm that a business is authorized to send SMS at volume. As of February 2025, the major carriers block unregistered A2P traffic from 10-digit numbers entirely, which makes registration a practical requirement for reliable delivery. Registered campaigns on Plura\u2019s carrier layer unlock higher daily message limits and stronger delivery rates, but 10DLC registration and TCPA consent remain separate obligations.<\/p>\n<h3>How should quiet-hours enforcement work across multiple states?<\/h3>\n<p>Quiet-hours rules vary by state, with the federal baseline and state-specific windows detailed in Step 5. Plura enforces the most restrictive applicable rule per recipient location automatically, using the contact\u2019s local time zone and queuing messages that fall outside the permitted window. Operators running multi-state campaigns should confirm their specific state-level obligations with qualified legal counsel.<\/p>\n<h3>What audit documentation should operators be able to produce?<\/h3>\n<p>A defensible TCPA audit trail for SMS should include, for every contact, the consent record with the exact disclosure text presented, the method of capture such as web form, keyword opt-in, or signed document, a tamper-evident timestamp in UTC format, the channel scope covered by the consent, DNC scrub logs showing which registries were checked and when, opt-out events with processing timestamps, and message delivery logs linked to the contact record. Plura\u2019s compliance dashboard exports this documentation in one click. Retention policies should align with the TSR\u2019s 5-year requirement mentioned in Step 1, and customers remain responsible for their own retention decisions and regulatory obligations while Plura provides the supporting infrastructure and logging layer.<\/p>\n<p><a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\">Review detailed pricing and throughput limits for your volume at plura.ai\/pricing.<\/a><\/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","protected":false},"excerpt":{"rendered":"<p>Plura AI runs consent checks, DNC scrubbing, and opt-out handling inside your CRM. See how to manage TCPA-compliant SMS at scale.<\/p>\n","protected":false},"author":106,"featured_media":1055,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-1056","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\/1056","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=1056"}],"version-history":[{"count":0,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/1056\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/1055"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=1056"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=1056"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=1056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}