{"id":1715,"date":"2026-08-25T05:05:40","date_gmt":"2026-08-25T05:05:40","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/missed-call-booking-compliance"},"modified":"2026-09-02T05:25:37","modified_gmt":"2026-09-02T05:25:37","slug":"missed-call-booking-compliance","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/missed-call-booking-compliance","title":{"rendered":"Missed Call Booking Compliance: SMS Rules Explained"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways for Missed-Call Booking Compliance<\/h2>\n<ul>\n<li>Missed-call booking compliance requires explicit opt-in, real-time DNC scrubbing, consent logging, and quiet-hours enforcement before any automated SMS follow-up.<\/li>\n<li>High-volume operators face significant TCPA exposure, with potential liability up to $1,500 per violation when recovery texts lack documented prior express written consent.<\/li>\n<li>Consent must be captured through an affirmative action at every inbound touchpoint and stored in a centralized, immutable registry that is ready for audit.<\/li>\n<li>Recovery messages must remain strictly transactional. Any promotional content reclassifies the message and triggers stricter written-consent requirements.<\/li>\n<li>Plura AI\u2019s carrier-grade compliance engine and stateful conversation database automatically enforce these controls from the first unanswered ring through confirmed booking, <a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">see how Plura AI can help your team support compliance<\/a>.<\/li>\n<\/ul>\n<h2>Consent Requirements After a Missed Call<\/h2>\n<p>Under 47 U.S.C. \u00a7 227, automated calls or texts require the called party\u2019s prior express consent before initiation.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> The consent tier depends on the content of the message.<\/p>\n<p>Prior express consent covers purely informational or transactional messages, such as a short acknowledgment of a missed call that offers help booking an appointment. Prior express written consent (PEWC) is a higher standard and applies to any message that includes or introduces an advertisement or constitutes telemarketing, per 47 C.F.R. \u00a7 64.1200(a)(2).<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Valid PEWC must be clear and unambiguous, state that consent is not a condition of purchase, identify the specific business authorized to contact the consumer, and be documented and stored.<\/p>\n<p>The workflow below outlines one way operators can structure consent capture on the first reply to a <a href=\"https:\/\/plura.ai\/home-services-demo\" target=\"_blank\" rel=\"noindex nofollow\">missed-call booking<\/a> attempt. Operators should consult qualified counsel to confirm this structure meets their specific obligations.<\/p>\n<ol>\n<li>Display a disclosure at every inbound touchpoint, such as a web form, IVR greeting, or booking page. The disclosure should state the business name, explain that automated texts may follow a missed call, and clarify that consent is not a condition of purchase. This disclosure creates the foundation for consent capture.<\/li>\n<li>After the disclosure appears, capture an affirmative action, such as an unchecked checkbox or a keyword reply, before sending any automated follow-up SMS. This step provides a clear record that the consumer agreed to receive automated texts.<\/li>\n<li>At the moment consent is captured, log the phone number, consent source, exact disclosure text shown, user reply, UTC timestamp, and channel. These fields create an evidentiary record that supports the consent claim.<\/li>\n<li>Store that record in a centralized consent registry, separate from CRM records, so it can be queried at dial time on every subsequent contact attempt. Centralization helps ensure that consent status is checked before each outbound message.<\/li>\n<\/ol>\n<p>Plura\u2019s compliance engine integrates with <a href=\"https:\/\/www.plura.ai\/guides\/ai-agency-communications\" target=\"_blank\">The Blacklist Alliance\u2019s TCPA Litigation Firewall for real-time DNC scrubbing and litigation protection<\/a>.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"3\">3<\/sup> Its stateful conversation database timestamps and stores consent records in an immutable ledger that can be exported for audit on demand.<\/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<p><sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup><\/p>\n<p><a href=\"https:\/\/plura.ai\/home-services-demo\" target=\"_blank\" rel=\"noindex nofollow\"><strong>Book a live demo with Plura to see the consent capture workflow in action.<\/strong><\/a><\/p>\n<h2>Automated Opt-In Flow for Booking Links<\/h2>\n<p>Automated opt-in for <a href=\"https:\/\/plura.ai\/home-services-demo\" target=\"_blank\" rel=\"noindex nofollow\">missed-call booking<\/a> relies on disclosure language that is specific, affirmative, and tied to a single named sender. Under the reinstated PEWC standard, consent must include the consumer\u2019s signature and clear disclosures about the nature of the consent and that robocalls or robotexts will be received from the identified party.<\/p>\n<p>Here is an example of permitted disclosure language for a web form or IVR:<\/p>\n<blockquote>\n<p>\u201cBy submitting this form [or pressing 1], you agree that [Business Name] may send you automated text messages at the number provided to help schedule your appointment. Consent is not a condition of purchase. Reply STOP at any time to opt out.\u201d<\/p>\n<p>The five-step workflow below shows one way operators can structure an <a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">AI SMS<\/a> opt-in flow with stateful memory handoff. Operators should consult qualified counsel to confirm this structure meets their specific obligations.<\/p>\n<ol>\n<li>Present the disclosure at the point of number collection, whether on a web form, booking page, or IVR prompt, before any automated message is sent. This step ensures the consumer sees the terms before opting in.<\/li>\n<li>Require an affirmative action, such as a checkbox or a keyword reply like \u201cYES,\u201d to confirm consent. Pre-checked boxes do not satisfy the affirmative-action standard and should not be used.<\/li>\n<li>Send a one-time confirmation SMS that restates the business name, the purpose of future messages, and opt-out instructions such as \u201cReply STOP to unsubscribe.\u201d This confirmation reinforces expectations and opt-out options.<\/li>\n<li>Write the consent record, including the phone number, campaign purpose, named sender, exact disclosure version, UTC timestamp, and IP or device metadata, to the centralized consent registry before any follow-up message is queued. This step links every future contact to a specific consent record.<\/li>\n<li>Pass the consent status and full interaction context to Plura\u2019s stateful conversation database so that every subsequent channel, including voice, SMS, or webchat, inherits the same consent record and conversation history. This approach prevents customers from repeating themselves and keeps consent aligned across channels.<\/li>\n<\/ol>\n<p>Plura\u2019s <a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">AI SMS<\/a> agents read from and write to this stateful database on every interaction. A consent record captured at web form submission is available at the moment of the first recovery text and at every touchpoint that follows.<\/p>\n<h2>TCPA Rules for Transactional Appointment Texts<\/h2>\n<p>The FCC classifies SMS message types by content rather than sender intent. <a href=\"https:\/\/foundgrove.com\/blog\/sms-lead-follow-up-tcpa-compliance-2026\" target=\"_blank\" rel=\"noindex nofollow\">An autodialed text to a cell phone requires prior express consent, while any text that includes or introduces an advertisement or constitutes telemarketing requires prior express written consent under 47 C.F.R. \u00a7 64.1200(a)(1) and (a)(2)<\/a>.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<p><a href=\"https:\/\/smtp2go.com\/blog\/transactional-sms\" target=\"_blank\" rel=\"noindex nofollow\">Adding promotional content such as discounts or coupons to a transactional message reclassifies the entire message as promotional under TCPA, which triggers the higher written-consent requirement and increases violation risk<\/a>. A short automated reply that acknowledges a missed call and offers help booking an appointment remains transactional. Any mention of a sale, discount, or new service converts the message to promotional.<\/p>\n<p>The workflow below outlines how operators can keep recovery messages strictly transactional. Operators should consult qualified counsel to confirm this structure meets their specific obligations.<\/p>\n<ol>\n<li>Limit the first recovery SMS to the business name, an acknowledgment of the missed call, and a direct booking link or offer to schedule. Exclude promotional language, discount codes, and new service announcements.<\/li>\n<li>Review every message template against the CTIA Messaging Principles and Best Practices three-tier classification. Conversational traffic relies on implied consent, informational traffic relies on express consent that may be oral, and promotional traffic requires express written consent.<\/li>\n<li>Route any message that contains a promotional element through the PEWC gate before sending. Confirm that a documented written consent record exists for that specific number and that specific sender.<\/li>\n<li>Maintain separate message templates for transactional and promotional flows in the workflow builder. Template-level separation helps enforce content classification and reduces reliance on individual agent judgment.<\/li>\n<\/ol>\n<h2>State Quiet-Hours and Time-Zone Controls for SMS<\/h2>\n<p>Federal TCPA rules restrict automated marketing messages before 8:00 a.m. or after 9:00 p.m. in the recipient\u2019s local time zone, per 47 C.F.R. \u00a7 64.1200.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Several states apply stricter windows. <a href=\"https:\/\/leadgen-economy.com\/blog\/dnc-scrubbing-operator-deep-dive-federal-state-rnd\" target=\"_blank\" rel=\"noindex nofollow\">Eleven states maintain separate Do Not Call lists that operators must scrub against in addition to the National Registry: Colorado, Florida, Indiana, Louisiana, Massachusetts, Missouri, Oklahoma, Pennsylvania, Tennessee, Texas, and Wyoming<\/a>.<\/p>\n<p>The three-step workflow below shows how operators can implement time-zone detection and quiet-hours blocking. Operators should consult qualified counsel to confirm this structure meets their specific obligations.<\/p>\n<ol>\n<li>Resolve the recipient\u2019s time zone at the point of number collection using IP geolocation or area-code mapping. Store the resolved time zone in the contact record alongside the consent data.<\/li>\n<li>Apply a pre-send gate that checks the current time in the recipient\u2019s resolved time zone against the federal 8 a.m. to 9 p.m. window and any applicable state-specific window before releasing any outbound SMS or voice contact.<\/li>\n<li>Queue messages that fall outside the permitted window for delivery at the next permitted time instead of dropping them. Log the queue event with a timestamp so the delay remains auditable.<\/li>\n<\/ol>\n<p>Plura\u2019s compliance engine enforces quiet-hours rules automatically through time-zone detection on every outbound contact. It applies state and federal calling-window restrictions across all campaigns without manual configuration for each state.<\/p>\n<h2>Consent Logging and Retention for Audit Readiness<\/h2>\n<p>Audit-ready consent logging depends on capturing specific fields at the moment of opt-in and storing them in an immutable, queryable record. <a href=\"https:\/\/agxntsix.ai\/guides\/tcpa-compliant-conversational-consent-outbound-ai-systems\" target=\"_blank\" rel=\"noindex nofollow\">An audit-safe consent record should capture the phone number, specific campaign purpose, named seller, exact disclosure version shown at opt-in, a UTC timestamp, IP or device metadata, and a full status history including any revocation events<\/a>. The TCPA statute of limitations runs four years, and the Telemarketing Sales Rule requires a five-year retention period under 16 C.F.R. \u00a7 310.5(a), effective May 16, 2024. Operators often retain records for at least five years to align with both standards.<\/p>\n<p>The table below compares manual and automated compliance processes across four operational dimensions. Operators should consult qualified counsel regarding their specific recordkeeping obligations.<\/p>\n<table>\n<thead>\n<tr>\n<th>Process<\/th>\n<th>Manual Approach<\/th>\n<th>Automated Approach (Plura)<\/th>\n<th>Key Risk if Manual<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Consent Capture<\/td>\n<td>Agent records opt-in verbally or in a spreadsheet, and the disclosure version is not tracked.<\/td>\n<td>Immutable ledger captures phone number, disclosure version, UTC timestamp, and channel at opt-in, <a href=\"https:\/\/www.plura.ai\/guides\/ai-communications-strategy\" target=\"_blank\">integrated with Blacklist Alliance for real-time screening<\/a>.<\/td>\n<td><a href=\"https:\/\/www.plura.ai\/guides\/ai-marketing-automation\" target=\"_blank\">$500 to $1,500 per violation under TCPA<\/a> if consent cannot be proven.<\/td>\n<\/tr>\n<tr>\n<td>DNC Scrub<\/td>\n<td>Batch scrub performed days before the campaign, which misses new registrations.<\/td>\n<td><a href=\"https:\/\/dialerguru.com\/dnc-scrubber-tcpa-compliance-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">Real-time scrub at the moment of dial against federal, state, and internal lists<\/a>.<\/td>\n<td><a href=\"https:\/\/leadgen-economy.com\/blog\/dnc-scrubbing-operator-deep-dive-federal-state-rnd\" target=\"_blank\" rel=\"noindex nofollow\">TSR civil penalty up to $53,088 per violation in 2025<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Quiet-Hours Check<\/td>\n<td>Agent manually checks time zone, which becomes error-prone at scale.<\/td>\n<td>Time-zone detection resolves the recipient\u2019s local time on every contact, and messages outside the permitted window are queued instead of dropped.<\/td>\n<td>Federal and state quiet-hours violations, TCPA applies the 8 a.m. to 9 p.m. local time restriction.<\/td>\n<\/tr>\n<tr>\n<td>Audit Export<\/td>\n<td>Records scattered across CRM, spreadsheets, and email, which requires manual assembly for legal review.<\/td>\n<td>One-click export of timestamped, immutable consent and scrub logs from a centralized registry.<\/td>\n<td>Inability to produce records in litigation or regulatory inquiry, <a href=\"https:\/\/agxntsix.ai\/guides\/double-opt-in-consent-outbound-ai-voice-systems\" target=\"_blank\" rel=\"noindex nofollow\">TCPA statute of limitations runs four years<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a href=\"https:\/\/plura.ai\/calculator\" target=\"_blank\"><strong>Run your numbers through Plura\u2019s ROI calculator to check your cost savings in real time.<\/strong><\/a><\/p>\n<h2>Audit-Ready Operations Checklist<\/h2>\n<p>The checklist below summarizes the operational controls described in this article. Operators can use it as a starting reference and should consult qualified counsel to confirm it covers their specific regulatory obligations.<\/p>\n<ol>\n<li>Confirm that a disclosure naming your business and describing automated SMS follow-up appears at every inbound touchpoint before any recovery text is sent.<\/li>\n<li>Require an affirmative opt-in action, such as an unchecked checkbox or keyword reply, before queuing any automated SMS after a missed call.<\/li>\n<li>Log every consent event with phone number, campaign purpose, named sender, exact disclosure text, UTC timestamp, IP or device metadata, and channel.<\/li>\n<li>Store consent records in a centralized registry, not inside individual CRM records, so they can be queried at dial time.<\/li>\n<li>Scrub every outbound number against the National Do Not Call Registry, applicable state DNC lists, and your internal suppression list in real time at the moment of contact, not in a prior batch run.<\/li>\n<li>Resolve the recipient\u2019s time zone at number collection and enforce the federal 8 a.m. to 9 p.m. window plus any applicable state-specific window on every outbound SMS and voice contact.<\/li>\n<li>Keep recovery message content strictly transactional, including business name, missed-call acknowledgment, booking link, and opt-out instruction. Exclude promotional language, discounts, and new service announcements.<\/li>\n<li>Honor opt-out requests received through any reasonable method within 10 business days per the FCC\u2019s April 2025 Consent Revocation Rule, and propagate suppression instantly across all connected systems.<\/li>\n<li>Retain consent records, DNC scrub logs, opt-out records with timestamps, and campaign records for a minimum of five years to align with TSR requirements.<\/li>\n<li>Conduct monthly audits of sampled contact records to verify that consent linkage, disclosure injection, DNC suppression, and quiet-hours enforcement are all functioning correctly across live campaigns.<\/li>\n<\/ol>\n<p><a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\"><strong>Compare Plura\u2019s plans and rates side by side at plura.ai\/pricing.<\/strong><\/a><\/p>\n<hr>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Does an inbound missed call create consent for an automated SMS follow-up?<\/h3>\n<p>An inbound call from a consumer does not automatically create consent for any automated SMS follow-up under the TCPA. The act of calling a business may support a transactional relationship, but any subsequent automated text initiated by the business requires its own consent analysis. A short, purely informational reply that acknowledges the missed call and offers help booking an appointment operates under a lower consent standard than a promotional message, yet operators still need a documented basis for that contact. Consent obtained through a prior web form, IVR disclosure, or booking page that explicitly covers automated follow-up texts provides a clearer documented basis. Operators should consult qualified counsel regarding their specific consent obligations before deploying any automated missed-call recovery workflow.<\/p>\n<h3>What records support a TCPA consent claim?<\/h3>\n<p>Litigation standards for TCPA consent documentation typically call for a record that includes the phone number, specific campaign purpose, named seller, exact disclosure text shown at opt-in, a UTC timestamp, IP or device metadata, and a full status history that includes any revocation events. Records should be stored in a centralized consent registry that can be queried at dial time, not scattered across CRM fields or spreadsheets. The Telemarketing Sales Rule requires retention of internal DNC records for five years, and the TCPA\u2019s statute of limitations on individual claims runs four years. Operators should consult qualified counsel to confirm their specific recordkeeping obligations and retention periods.<\/p>\n<h3>How does Plura AI support real-time DNC scrubbing and consent logging?<\/h3>\n<p>Plura\u2019s compliance engine checks every outbound number against federal and state DNC registries and internal suppression lists at the moment of contact, not in a prior batch run. Consent records are written to an immutable ledger that captures the phone number, disclosure version, UTC timestamp, and channel at opt-in. The platform integrates with The Blacklist Alliance\u2019s TCPA Litigation Firewall for real-time litigator and DNC screening. Quiet-hours enforcement runs automatically through time-zone detection on every outbound contact. Audit-ready exports of consent and scrub logs are available on demand from the compliance dashboard. Plura provides this infrastructure, and operators remain responsible for their own compliance posture and regulatory obligations.<\/p>\n<h3>What is the difference between transactional and promotional SMS in missed-call recovery?<\/h3>\n<p>The FCC classifies SMS messages by content rather than sender intent. A transactional or informational message is triggered by a consumer\u2019s own action and contains no promotional content, such as a short text that acknowledges a missed call and offers a booking link. A promotional message includes or introduces an advertisement or constitutes telemarketing, such as a discount offer or a new service announcement. Adding any promotional element to an otherwise transactional message reclassifies the entire message as promotional and triggers the prior express written consent requirement. Operators should review every recovery message template against this content-based standard and consult qualified counsel before deployment.<\/p>\n<h3>Which states apply stricter SMS quiet-hours rules than the federal window?<\/h3>\n<p>Several states impose calling and texting restrictions that are stricter than the federal TCPA window or that apply to a broader set of communications. As noted earlier, eleven states maintain separate DNC registries in addition to the National Registry, which adds another layer of list management. State-specific quiet-hours rules vary and change over time. Operators running national campaigns should review applicable state statutes and consult qualified counsel to confirm the current rules for each state in which they contact consumers. Plura\u2019s compliance engine is pre-loaded with 50-plus state rule sets and applies them automatically through time-zone detection on every outbound contact.<\/p>\n<\/blockquote>\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=\"25\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"3\">3<\/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\/text-to-call-compliance\" target=\"_blank\">Text to Call Compliance: TCPA Rules for SMS and Voice<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/tcpa-compliant-crm-sms\" target=\"_blank\">TCPA-Compliant CRM SMS: What Your Platform Must Do<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-booking-call-centers\" target=\"_blank\">Missed Call Booking for Call Centers: Stop Losing Leads<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/missed-call-booking-software\" target=\"_blank\">Missed Call Booking Software and AI Voice Booking Agents<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/crm-sms-dnc-compliance-2026\" target=\"_blank\">CRM SMS DNC Compliance: Automate TCPA Rules and Opt-Outs<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Avoid TCPA exposure on automated SMS follow-ups. Plura AI enforces opt-in, DNC scrubbing, and consent logging through every missed call recovery.<\/p>\n","protected":false},"author":106,"featured_media":1714,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-1715","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\/1715","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=1715"}],"version-history":[{"count":1,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/1715\/revisions"}],"predecessor-version":[{"id":2156,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/1715\/revisions\/2156"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/1714"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=1715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=1715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=1715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}