{"id":138,"date":"2026-05-21T19:08:31","date_gmt":"2026-05-21T19:08:31","guid":{"rendered":"https:\/\/plura.ai\/articles\/5-minute-lead-response-software\/"},"modified":"2026-09-02T05:26:37","modified_gmt":"2026-09-02T05:26:37","slug":"5-minute-lead-response-software","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/5-minute-lead-response-software","title":{"rendered":"5 Minute Lead Response Software: AI Auto-Contact Guide"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI | Last updated: August 25, 2026<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways for Speed-to-Lead Operators<\/h2>\n<ul>\n<li>Automated contact in under five seconds lifts connection and conversion rates far above the 47-hour industry average.<\/li>\n<li>Notification-only tools depend on human availability, while AI contact-center platforms start voice and SMS outreach automatically.<\/li>\n<li>Plura AI delivers sub-five-second contact across voice, SMS, RCS, and webchat on 100% U.S. carrier infrastructure with built-in controls that support TCPA, DNC, HIPAA, SOC 2, ISO, GDPR, and SHAKEN\/STIR.<sup data-disclaimer-ids=\"22,23\" data-disclaimer-indexes=\"1,2\">1,2<\/sup><\/li>\n<li>Stateful conversation memory across every channel means leads never repeat themselves, which improves qualification and close rates.<\/li>\n<li><a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">See sub-five-second automated contact in action<\/a> with a live demo on your own lead flows.<\/li>\n<\/ul>\n<h2>The Problem: Slow Lead Response Drains Revenue<\/h2>\n<p><a href=\"https:\/\/fusionsync.ai\/posts\/b2b-saas-lead-response-benchmarks-2026\" target=\"_blank\" rel=\"noindex nofollow\">Optifai&#8217;s 2026 Sales Ops Benchmark across 939 B2B companies<\/a> puts the average lead response time at 47 hours.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> Only 23% of companies respond within five minutes. The cost of that gap is concrete: <a href=\"https:\/\/www.plura.ai\/calculator\" target=\"_blank\">benchmarks cited by Plura<\/a> show that contacting a lead within five minutes makes them up to 100 times more likely to connect.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> Responding within 60 seconds lifts conversions by 391%.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<p><a href=\"https:\/\/fusionsync.ai\/posts\/b2b-saas-lead-response-benchmarks-2026\" target=\"_blank\" rel=\"noindex nofollow\">The same Optifai benchmark<\/a> found a 32% close rate for leads contacted in under five minutes versus 12% for leads contacted after 24 hours.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> That 2.6x gap in close rate tracks directly to response time, not product quality or pricing.<\/p>\n<p>Notification-only tools sit at the center of this problem. A platform that alerts a human representative when a lead arrives does not contact the lead. It starts a timer. The representative still has to open the notification, locate the lead record, dial or compose a message, and wait for a response. By the time that sequence completes, the lead has usually heard from a competitor or moved on. <a href=\"https:\/\/www.elev8operations.com\/guides\/speed-to-lead-statistics-2026\" target=\"_blank\" rel=\"noindex nofollow\">The 2007 MIT\/InsideSales.com Lead Response Management study<\/a> shows that leads called within five minutes are 21 times more likely to qualify than those called after 30 minutes.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup><\/p>\n<p>The regulatory environment adds a second layer of pressure. The FCC&#8217;s Notice of Proposed Rulemaking (CG Docket No. 26-52) proposes capping offshore customer-service calls at 30% and limiting offshore handling of sensitive consumer data. State-level onshoring laws in New York, New Jersey, Connecticut, Missouri, and Florida already restrict offshore handling of medical, financial, and consumer data. Operators running notification-only tools that depend on offshore labor or foreign infrastructure now carry compliance exposure on top of the conversion gap. These dual pressures, speed and regulatory risk, point operators toward a different architecture.<\/p>\n<h2>Solution Category: AI Contact-Center Platforms That Auto-Contact<\/h2>\n<p>The relevant product category is not lead notification software. It is AI contact-center platforms that initiate voice and SMS contact automatically, without a human in the initiation loop.<\/p>\n<p>Plura AI operates in this category. When a lead submits a form, Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-voice-demo\" target=\"_blank\" rel=\"noindex nofollow\">AI voice agent<\/a> and <a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">AI SMS<\/a> agent initiate contact in under five seconds across both channels at the same time. The AI voice agent handles inbound and outbound calls on Plura&#8217;s own FCC-licensed audio bridging carrier, with branded caller ID and STIR\/SHAKEN authentication on every call. The AI SMS agent runs the same conversation workflow and reads from the same stateful memory, so a lead who received a text at 9 a.m. is recognized when the call comes at noon.<\/p>\n<p>Channel orchestration, <a href=\"https:\/\/plura.ai\/managed-workflows\" target=\"_blank\" rel=\"noindex nofollow\">managed workflows<\/a>, and <a href=\"https:\/\/plura.ai\/business-intelligence\" target=\"_blank\" rel=\"noindex nofollow\">conversation intelligence<\/a> sit on top of a Stateful Conversation Database that holds context across every touchpoint. Every interaction is keyed to the customer by phone number, email, or ID. The AI does not start over on each channel. It continues the conversation.<\/p>\n<p><a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">Book a live demo with Plura<\/a> to see instant automated engagement on your own lead flows.<\/p>\n<h2>Neutral Evidence: 2026 Lead-Response Data and Regulation<\/h2>\n<p>The data on lead response speed is consistent across multiple independent sources:<\/p>\n<ul>\n<li><a href=\"https:\/\/fusionsync.ai\/posts\/b2b-saas-lead-response-benchmarks-2026\" target=\"_blank\" rel=\"noindex nofollow\">Optifai&#8217;s 2026 Sales Ops Benchmark (n=939 B2B companies)<\/a> confirms the 47-hour industry average and the 2.6x close-rate advantage for sub-five-minute response cited earlier.<\/li>\n<li>The <a href=\"https:\/\/www.plura.ai\/glossary\/speed-to-lead\" target=\"_blank\">Lead Response Management Study by Dr. James Oldroyd at MIT, analyzed by InsideSales.com<\/a>, provides the foundational research behind the 21x qualification advantage and 100x connection likelihood for sub-five-minute response.<\/li>\n<li>Velocify\u2019s (formerly Leads360) study of nearly 3.5 million leads found that calling within one minute improves conversion rates by 391% compared to later times.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup><\/li>\n<li>A 2007 MIT\/InsideSales study of 1,000 demo requests found that 63.5% of B2B firms never replied to leads at all.<\/li>\n<\/ul>\n<p>On the regulatory side, the FCC&#8217;s NPRM CG Docket No. 26-52 and companion federal legislation including the Keep Call Centers in America Act (S.2495) and the Foreign Robocall Elimination Act (S.2666) extend the federal regulatory perimeter around offshore operations and foreign infrastructure. Operators whose lead response workflows depend on offshore labor or non-U.S. infrastructure face growing exposure under these frameworks. Consulting qualified counsel on the specific implications for your operation is advisable.<\/p>\n<h2>Six Pain\/Solution Pairings for Contact-Center Leaders<\/h2>\n<p><strong>Slow response vs. automated immediate engagement.<\/strong> The average operator takes 47 hours to contact a lead, which falls far outside the high-conversion window. Plura initiates voice and SMS contact in under five seconds, 24 hours a day, seven days a week, with no human in the initiation loop. The <a href=\"https:\/\/www.plura.ai\/glossary\/speed-to-lead\" target=\"_blank\">qualification odds drop by an order of magnitude<\/a> between a five-minute and a thirty-minute callback, so response times measured in seconds set the new baseline.<\/p>\n<p><strong>Fragmented channels vs. unified conversation management.<\/strong> Most operators run separate tools for voice, SMS, and chat, each with its own memory. Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-voice-demo\" target=\"_blank\" rel=\"noindex nofollow\">AI voice agent<\/a>, <a href=\"https:\/\/plura.ai\/ai-sms-leads\" target=\"_blank\" rel=\"noindex nofollow\">AI SMS<\/a> agent, and <a href=\"https:\/\/plura.ai\/plura-webchat\" target=\"_blank\" rel=\"noindex nofollow\">AI webchat<\/a> share a single Stateful Conversation Database. Every channel inherits the full history of every prior touchpoint.<\/p>\n<p><strong>Rising labor costs vs. scalable automation.<\/strong> A 15-agent human contact center running at 40% talk utilization costs approximately $60,000 per month at standard rates. <a href=\"https:\/\/www.plura.ai\/calculator\" target=\"_blank\">Plura&#8217;s default calculator scenario<\/a> shows six AI agents replacing 15 humans at $14,400 per month, with 100% talk utilization and no taxes, benefits, or commissions overhead.<\/p>\n<p><strong>Inconsistent quality vs. standardized workflows.<\/strong> Human agents drift from scripts over time. Plura&#8217;s <a href=\"https:\/\/plura.ai\/managed-workflows\" target=\"_blank\" rel=\"noindex nofollow\">managed workflows<\/a> run the same conversation logic on every contact, with BATNA-style negotiation guardrails that define the floor and ceiling within which the AI operates. Quality remains consistent from Monday morning through Friday afternoon.<\/p>\n<p><strong>Compliance complexity vs. built-in controls.<\/strong> Plura supports TCPA compliance, DNC compliance, HIPAA, SOC 2, ISO certification, GDPR, and SHAKEN\/STIR caller ID verification as first-class platform layers.<sup data-disclaimer-ids=\"22,23\" data-disclaimer-indexes=\"1,2\">1,2<\/sup> Every outbound contact is checked against federal and state DNC registries before dial. Consent records are timestamped and immutable. Quiet-hours rules enforce automatically through time-zone detection. Customers are responsible for their own compliance obligations; Plura provides the infrastructure that supports those obligations.<\/p>\n<p><strong>Low contact rates vs. carrier-owned identity and deliverability.<\/strong> Most AI voice tools route calls through third-party CPaaS providers and inherit shared number reputation. Plura is its own FCC-licensed audio bridging carrier. Branded caller ID is issued at the carrier level. STIR\/SHAKEN authentication runs on every outbound call. Calls present with the company&#8217;s name rather than &#8220;Spam Likely.&#8221;<\/p>\n<h2>Category Analysis: How Auto-Contact Compares<\/h2>\n<p>Every figure is drawn from published sources or Plura&#8217;s documented platform capabilities.<\/p>\n<p>Plura AI, as an auto-contact platform, initiates contact in under five seconds, supports voice, SMS, RCS, and webchat on one stateful database, includes built-in controls that support federal and state compliance requirements, operates on an FCC-licensed carrier with 100% U.S. infrastructure by architecture, and scales instantly with no hiring or training cycle.<\/p>\n<p>Notification-only tools depend on human availability after notification. They typically offer single-channel notification, place compliance responsibility on the operator with varying tool support, usually use third-party CPaaS, and scale only as fast as human headcount.<\/p>\n<p>Offshore BPOs show variable time to first contact subject to staffing and time-zone gaps. They support voice and email with SMS varying by vendor, carry exposure under FCC NPRM CG Docket No. 26-52 and state onshoring laws, rely on foreign infrastructure subject to FCC NPRM proposals, and scale via headcount with regulatory exposure growing with scale.<\/p>\n<p>Onshore human call centers show variable time to first contact subject to queue and agent availability. They focus on voice with SMS and chat requiring separate tooling, operate onshore with compliance posture varying by vendor, depend on U.S. carrier partners, and scale via headcount with a 2 to 4 week training ramp per hire.<\/p>\n<h2>Realistic Risks and Due-Diligence Criteria<\/h2>\n<p>AI contact-center platforms deliver measurable results when deployed correctly. They also carry implementation risks that operators should evaluate before committing to a vendor.<\/p>\n<ul>\n<li><strong>Implementation complexity.<\/strong> A simple inbound qualification flow can go live in days. A multi-step intake with branching logic and sensitive-data handling runs closer to one to two months. Operators should map their conversation requirements before selecting a platform.<\/li>\n<li><strong>Data quality.<\/strong> AI agents are only as accurate as the lead data they receive. Incomplete or stale records produce lower contact rates regardless of response speed. List validation and enrichment at the point of capture reduce this risk.<\/li>\n<li><strong>Workflow design.<\/strong> Conversation logic that works in a demo environment may not hold under real-world objection patterns. Platforms that iterate workflows continuously after launch outperform those that hand off a static build.<\/li>\n<li><strong>Regulatory fit.<\/strong> TCPA, DNC, HIPAA, and state-level frameworks describe specific conditions for automated voice and SMS outreach. Operators should consult qualified counsel to assess how any platform deployment intersects with their specific regulatory obligations.<\/li>\n<li><strong>Vendor dependency.<\/strong> A platform that owns its carrier stack, its conversation memory, and its compliance engine is structurally different from one that wraps third-party APIs. Vendor consolidation reduces integration risk but increases dependency on a single provider&#8217;s uptime and roadmap.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">Book a live demo with Plura<\/a> to walk through implementation timelines and workflow requirements for your specific operation.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How does 5 minute lead response software differ from notification-only tools?<\/h3>\n<p>Notification-only tools alert a human representative when a lead arrives, and the human then initiates contact. Five minute lead response software that operates as an auto-contact platform initiates voice and SMS contact automatically, without a human in the loop. Plura&#8217;s AI voice agent and AI SMS agent contact leads in under five seconds from the moment of form submission, 24 hours a day. The distinction matters because lead intent has a short half-life. Qualification odds drop significantly after the first five minutes, and a notification that reaches a representative who is on another call, in a meeting, or off-shift does not close that gap.<\/p>\n<h3>What channels does Plura support for automated lead contact?<\/h3>\n<p>Plura supports voice, SMS, RCS (Rich Communication Services), and webchat. All four channels share a single Stateful Conversation Database, so a lead who receives an SMS at 9 a.m. is recognized when the AI voice agent calls at noon. The AI does not restart the conversation on each channel. It continues from where the prior interaction ended, including any qualification data, objections raised, or offers made.<\/p>\n<h3>How does Plura support compliance for automated voice and SMS outreach?<\/h3>\n<p>Plura supports TCPA compliance, DNC compliance, HIPAA, SOC 2, ISO certification, GDPR, and SHAKEN\/STIR caller ID verification as built-in platform layers. Every outbound contact is checked against federal and state DNC registries before dial. Consent records are timestamped, immutable, and exportable for audit. Quiet-hours rules enforce automatically through time-zone detection. Operators are responsible for their own compliance obligations and should consult qualified counsel on how these platform capabilities apply to their specific regulatory situation. Plura provides the infrastructure, and compliance posture downstream of that remains the customer&#8217;s responsibility.<\/p>\n<h3>What integration requirements does Plura have?<\/h3>\n<p>Plura connects to 50+ tools across CRM, calendar, attribution, payment, document, and data enrichment categories, including HubSpot, Salesforce, Zoho, Google Calendar, Calendly, Stripe, DocuSign, and Zapier. The full directory is at <a href=\"https:\/\/plura.ai\/integrations\" target=\"_blank\" rel=\"noindex nofollow\">plura.ai\/integrations<\/a>. Workflow design uses a no-code visual canvas, so operators can configure conversation logic, routing rules, and post-call actions without engineering resources.<\/p>\n<h3>When does the AI hand off to a human agent?<\/h3>\n<p>Plura&#8217;s workflows include explicit escalation rules. When a customer&#8217;s response falls outside the workflow&#8217;s defined paths, such as an unfamiliar request, a sensitive disclosure, or a high-stakes objection, the AI warm-transfers the call to a U.S. agent, flags the conversation in the Unified Inbox, or routes to a designated escalation queue. Sensitive data including protected health information, payment data, and personally identifiable information is redacted at the field level and routed through HIPAA-aligned channels. The AI does not improvise on outcomes that carry compliance or business risk.<\/p>\n<h2>Conclusion: How to Evaluate 5 Minute Lead Response Software<\/h2>\n<p>The 47-hour industry average for lead response reflects an architecture problem, not a lack of tools. Notification-only products cannot close the gap because they depend on human availability at the moment of lead arrival. Immediate AI-initiated contact requires a platform that starts voice and SMS without a human in the loop, holds conversation memory across every channel, and enforces compliance controls before each outbound contact.<\/p>\n<p>Operators evaluating 5 minute lead response software can apply five criteria:<\/p>\n<ul>\n<li><strong>Does the platform initiate contact automatically, or does it notify a human to initiate?<\/strong> Only auto-contact platforms can achieve sub-five-second response at scale.<\/li>\n<li><strong>Does the platform own its carrier stack?<\/strong> Branded caller ID, STIR\/SHAKEN authentication, and spam-label remediation require carrier-level control. Platforms that wrap third-party CPaaS providers cannot issue caller ID under their own identity.<\/li>\n<li><strong>Is conversation memory stateful across channels?<\/strong> A lead who texted at 9 a.m. should not have to re-explain themselves when the call comes at noon.<\/li>\n<li><strong>Are compliance controls built into the platform or bolted on?<\/strong> TCPA compliance, DNC compliance, HIPAA, SOC 2, ISO certification, GDPR, and SHAKEN\/STIR caller ID verification should be enforced before each contact, not managed as a separate workflow.<\/li>\n<li><strong>Does the platform run on 100% U.S. infrastructure?<\/strong> The FCC NPRM CG Docket No. 26-52 and state onshoring laws create regulatory exposure for any operator whose lead response workflow touches foreign infrastructure.<\/li>\n<\/ul>\n<p>Plura AI meets all five criteria. Its FCC-licensed carrier infrastructure, stateful cross-channel memory, and built-in compliance controls form the operational foundation for response times measured in seconds, not hours.<\/p>\n<p><a href=\"https:\/\/www.plura.ai\/calculator\" target=\"_blank\">Run your numbers through Plura&#8217;s ROI calculator to check your cost savings in real time.<\/a><\/p>\n<p><a href=\"https:\/\/www.plura.ai\/pricing\" target=\"_blank\" rel=\"noindex nofollow\">Compare Plura&#8217;s plans and rates side by side 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<section data-read-next=\"true\">\n<h2>Read Next<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/contact-center-ai-speed-lead\" target=\"_blank\">Contact Center AI Speed to Lead: Sub-5-Second Responses<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/ai-lead-under-5-minutes\" target=\"_blank\">AI Lead Response in Under 5 Minutes: A 7-Step Guide<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/ai-lead-response-5-minutes\" target=\"_blank\">AI Lead Response Under 5 Minutes: Beat the 5-Minute Rule<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/top-lead-response-apps-2026\" target=\"_blank\">Best Lead Response Apps for Sub-5-Second Contact<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/ai-answering-service-speed-lead\" target=\"_blank\">AI Answering Service Speed to Lead: Respond in 5 Seconds<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Plura AI auto-contacts leads in under 5 minutes via voice, SMS, and webchat. See how AI contact centers close more deals. Book a demo today.<\/p>\n","protected":false},"author":106,"featured_media":137,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-138","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-contact-centers"],"_links":{"self":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/138","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=138"}],"version-history":[{"count":2,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/138\/revisions"}],"predecessor-version":[{"id":2166,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/138\/revisions\/2166"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/137"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}