{"id":180,"date":"2026-05-24T05:12:13","date_gmt":"2026-05-24T05:12:13","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/bcid-authorized-partners\/"},"modified":"2026-05-24T05:12:13","modified_gmt":"2026-05-24T05:12:13","slug":"bcid-authorized-partners","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/bcid-authorized-partners","title":{"rendered":"BCID Authorized Partners: Roles, Ecosystem, and Options"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI<\/em><\/p>\n<h2>Key Takeaways for BCID Decision-Makers<\/h2>\n<ul>\n<li>\n<p>BCID authorized partners perform signing, vetting, or onboarding functions within the CTIA ecosystem so calls display verified identity on recipient devices.<\/p>\n<\/li>\n<li>\n<p>Plura AI operates as an FCC-licensed audio bridging carrier that issues branded caller ID at the carrier level, which reduces third-party wrapper costs and closes common compliance gaps.<\/p>\n<\/li>\n<li>\n<p>High-volume operators in 2026 should evaluate partner structures based on STIR\/SHAKEN authentication depth, branded caller ID issuance model, real-time DNC scrubbing, and U.S. infrastructure posture.<\/p>\n<\/li>\n<li>\n<p>BCID delivers dynamic, carrier-authenticated rich call data that improves answer rates and reduces spam labeling compared to legacy CNAM systems.<\/p>\n<\/li>\n<li>\n<p>Plura\u2019s direct carrier path enables stateful conversation memory across channels and comprehensive compliance support; <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.plura.ai\/plura-webchat\">explore Plura\u2019s integrated solution<\/a> to streamline branded calling operations.<\/p>\n<\/li>\n<\/ul>\n<h2>How Branded Calling ID Works in Practice<\/h2>\n<p>Branded Calling ID is an open, interoperable ecosystem developed under CTIA governance that allows enterprises to display verified identity information, including business name, logo, and reason for the call, on a recipient\u2019s smartphone before they answer.<\/p>\n<p>BCID runs on top of the STIR\/SHAKEN (Secure Telephone Identity Revisited \/ Signature-based Handling of Asserted information using toKENs) framework. The <a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/www.fcc.gov\/call-authentication\">FCC mandates that voice service providers implement STIR\/SHAKEN caller ID authentication on IP networks<\/a>, with the core mandate adopted in 2020. BCID extends that authentication layer by attaching rich brand data to the authenticated call signal, so terminating carriers and devices can render the enterprise\u2019s identity rather than an unknown number.<\/p>\n<p>Operators in 2026 are shifting from CPaaS (Communications Platform as a Service) wrappers, where branded caller ID is bolted on through a third-party reseller, to end-to-end FCC-licensed carrier stacks where identity is issued at origination. That architectural difference sets the cost structure, onboarding speed, and depth of compliance enforcement available at the carrier level.<\/p>\n<h2>BCID Ecosystem Roles and Operator Outcomes<\/h2>\n<p>The BCID ecosystem assigns distinct responsibilities to three partner types. Understanding each role is the prerequisite for evaluating any vendor or infrastructure decision. The table below maps each role to its core responsibilities and the specific operator outcome it enables, so you can see which partner functions your infrastructure requires.<\/p>\n<table style=\"min-width: 75px\">\n<colgroup>\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\"><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Role<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Responsibilities<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Operator Outcome<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p><strong>Signing Agent<\/strong><\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Generates cryptographic signatures on the SHAKEN PASSporT (Personal ASSertion Token) that terminating service providers rely on to verify call authenticity. Manages the PKI (Public Key Infrastructure) trust chain.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Calls authenticate at the carrier level, which reduces spam-label risk and supports STIR\/SHAKEN attestation requirements.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p><strong>Vetting Agent<\/strong><\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Validates that enterprise callers are who they claim to be and have the right to use a specific display name, logo, and call reason. Performs KYC (Know Your Customer)-style identity verification aligned to CTIA standards.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Brand identity is verified before deployment, which supports carrier acceptance and reduces the risk of fraudulent use of the enterprise\u2019s identity.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p><strong>Onboarding Agent<\/strong><\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Collects enterprise registrant information and conveys it to approved vetting agents. Manages the intake workflow from initial registration through vetting handoff.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Branded calling campaigns reach production faster, with a structured intake process that feeds directly into the vetting pipeline.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Operators should evaluate any partner against signature support, trust-chain compatibility, identity validation depth, and the ability to deliver into downstream carrier ecosystems at scale.<\/p>\n<h2>What Branded Calling ID Replaces<\/h2>\n<p>Branded Calling ID is distinct from CNAM (Caller Name), which delivers a static text string through a legacy database lookup. BCID delivers dynamic, carrier-authenticated rich call data that renders on modern iOS and Android devices and gives recipients clear context before they answer.<\/p>\n<p>The practical problem BCID solves is spam labeling. When a legitimate enterprise call is flagged as \u201cSpam Likely,\u201d the pickup rate collapses. Spam-label remediation, the process of identifying and correcting erroneous spam classifications at the carrier level, operates as a parallel function that BCID-capable partners and FCC-licensed carriers can perform.<\/p>\n<p>Operators without carrier-level access must route remediation requests through intermediaries, which adds time and cost to each incident. That delay directly affects answer rates and customer experience for outbound teams. Operators must also select from approved call reasons during registration, which constrains campaign design but supports carrier acceptance and consumer trust.<\/p>\n<h2>How to Choose the Right BCID Partner<\/h2>\n<p>Once you understand how BCID works and which identity elements you can display, the next decision is which partner or infrastructure model can deliver those capabilities at your scale. The selection decision maps to four operational variables, and each one affects the next.<\/p>\n<p>Start with <strong>STIR\/SHAKEN authentication depth<\/strong>. Confirm the partner supports full A-attestation, which indicates the provider knows the caller\u2019s identity and their right to use the number, and delivers signing into the downstream carrier ecosystems your traffic reaches.<\/p>\n<p>That authentication layer determines the <strong>branded caller ID issuance model<\/strong>. Evaluate whether the partner issues branded caller ID through direct carrier relationships or through a reseller chain. Each additional layer adds cost and slows spam-label remediation when issues appear.<\/p>\n<p>Those economics connect directly to <strong>real-time DNC scrubbing<\/strong>. Assess whether DNC (Do Not Call) scrubbing is enforced at the carrier level before dial or applied as a post-processing step. Pre-dial enforcement at origination is generally viewed as a more defensible posture. Operators should consult qualified counsel regarding their specific DNC obligations.<\/p>\n<p>Finally, review <strong>U.S. infrastructure posture<\/strong>. The FCC NPRM (Notice of Proposed Rulemaking, CG Docket No. 26-52) proposes restrictions on offshore handling of sensitive consumer data. Operators should verify where each partner stores and processes call data. Consult qualified counsel for guidance on how these proposals may apply to your operations.<\/p>\n<h2>Branded Caller ID Pricing Structures<\/h2>\n<p>BCID pricing structures vary by partner role and delivery model. Vetting agents typically charge a one-time or annual identity verification fee per brand. Signing agents usually charge on a per-call or per-signature basis. Onboarding agents may bundle fees into a setup charge or pass through vetting costs.<\/p>\n<p>BCID offers transparent reporting and pricing with monthly call delivery reporting, and brands only pay for data that is delivered, which aligns financial incentives between operators and partners.<\/p>\n<p>The cost structure changes materially when an operator works with an FCC-licensed carrier that issues branded caller ID directly. The wrapper tax, the per-call margin that CPaaS resellers add when they sit between the originating carrier and the enterprise, is removed. For high-volume operators running hundreds of thousands of calls per month, that per-call delta compounds into a significant annual cost difference.<\/p>\n<p>Operators evaluating total cost of ownership should model both the per-call rate and the remediation cost structure before selecting a partner type. That model should include answer-rate lift, spam-label remediation effort, and any onshoring requirements driven by counsel.<\/p>\n<h2>BCID Signing Agent vs. Vetting Agent<\/h2>\n<p>Signing and vetting agents are frequently conflated, yet they perform distinct functions with different operator impacts. Treat them as separate decisions when you design your stack.<\/p>\n<p>A <strong>Signing Agent<\/strong> operates at the cryptographic layer. It generates the PASSporT signature that travels with the call through the network, which allows terminating carriers to verify that the call originated from an authenticated source. Signing agents interact with the PKI trust chain and must maintain high availability, because signature latency directly affects call setup time. SecureG\u2019s signing service delivers low latency signing, which illustrates the performance standard operators can apply when evaluating signing partners.<\/p>\n<p>A <strong>Vetting Agent<\/strong> operates at the identity layer. It verifies that the enterprise claiming a display name, logo, and call reason is who it says it is and has the right to use those assets. Numeracle participates in CTIA\u2019s BCID as a trusted Vetting Partner, performing KYC-style verification aligned to carrier-accepted standards.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup> Vetting is a prerequisite for signing, so an enterprise cannot receive authenticated branded calling without first passing vetting.<\/p>\n<p>The operator impact of each role differs. A signing failure affects every call in real time. A vetting failure blocks the entire branded calling program until identity is re-established. Both functions require partners with documented uptime SLAs, audit trails, and clear escalation paths.<\/p>\n<h2>Compliance and Onshoring Implications for BCID<\/h2>\n<p>Several regulatory developments in 2026 affect how operators structure their BCID and voice infrastructure. This section describes those frameworks neutrally. Operators should consult qualified counsel regarding their specific obligations.<\/p>\n<p>The <a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/www.fcc.gov\/call-authentication\">FCC requires all voice service providers to file robocall mitigation plans and compliance certifications in the FCC Robocall Mitigation Database<\/a>, including provider role in the call chain and details of any prior robocall enforcement actions.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> BCID implementation does not substitute for this filing requirement.<\/p>\n<p>FCC NPRM CG Docket No. 26-52 proposes capping offshore customer-service calls and restricting offshore handling of sensitive consumer data. The Keep Call Centers in America Act (S.2495) and the Foreign Robocall Elimination Act (S.2666) extend the federal regulatory perimeter. State-level laws in New York, New Jersey, Connecticut, Missouri, and Florida already address offshore handling of medical, financial, and consumer data. Operators with offshore infrastructure dependencies or offshore vendor contracts should review these frameworks with counsel.<\/p>\n<p>The <a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/www.fcc.gov\/consumers\/guides\/spoofing-and-caller-id\">Truth in Caller ID Act describes restrictions on transmitting misleading or inaccurate caller ID information with intent to defraud, cause harm, or wrongly obtain anything of value, with penalties of up to $10,000 per violation<\/a>.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> BCID\u2019s vetting and signing architecture is designed to support compliance with this framework by anchoring displayed identity to verified enterprise credentials.<\/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>Implementation Roadmap for High-Volume Operators<\/h2>\n<p>High-volume operators benefit from a structured rollout plan for BCID. The steps below build on each other, so treat them as a sequence rather than isolated tasks.<\/p>\n<p>Start by auditing interaction volume and confirm daily call volume meets the threshold where branded caller ID economics are favorable. Operators running fewer than 500 daily interactions may find setup costs disproportionate to pickup-rate lift.<\/p>\n<p>Once volume justifies the investment, assess data quality. Branded calling requires accurate, deduplicated contact records, because stale or duplicated numbers increase the risk of DNC violations and reduce the ROI of any answer-rate improvement.<\/p>\n<p>With cleaner data in place, map consent records. Verify that express written consent is documented, timestamped, and audit-ready for every contact in your outbound pool. Consult qualified counsel on consent requirements that apply to your vertical and call type.<\/p>\n<p>Next, evaluate carrier infrastructure. Determine whether your current voice provider can issue branded caller ID at the carrier level or routes through a CPaaS reseller. That answer sets your remediation speed and per-call cost structure.<\/p>\n<p>After you understand the carrier posture, select partner roles. Identify whether you need a signing agent, vetting agent, onboarding agent, or a carrier that performs all three functions natively.<\/p>\n<p>Then define escalation paths. Document what happens when a spam label appears, when a signature fails, or when a vetting dispute arises. Partners without documented SLAs for these scenarios create operational risk at scale.<\/p>\n<p>Finally, review U.S. infrastructure posture. Confirm where call data, recordings, and brand assets are stored and processed, and cross-reference that map against applicable state and federal frameworks with counsel.<\/p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/plura.ai\/pricing\"><strong>Calculate your total cost of ownership across these implementation variables<\/strong><\/a> to see how your current stack compares.<\/p>\n<h2>Branded Caller ID Outcomes You Can Expect<\/h2>\n<p>Independent data sets show consistent answer-rate gains from branded calling. Enterprises that have deployed branded caller ID solutions have experienced call center answer rates increasing by 25%, along with a quadrupling of median call duration.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup> Organizations using branded calling have achieved increased answer rates in some deployments. TNS has delivered more branded calls through its Enterprise Branded Calling solution, which reflects accelerating adoption among high-volume operators.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup><\/p>\n<p>Spam-label remediation protects these gains over time. A branded calling program that is not paired with active spam-label monitoring will see pickup rates erode as carrier filters adapt. Operators should treat remediation as an ongoing operational function, not a one-time setup step.<\/p>\n<h2>Plura\u2019s Direct Carrier Path for Branded Calling<\/h2>\n<p>Plura AI is its own FCC-licensed audio bridging carrier. Voice originates on Plura\u2019s domestic infrastructure, not through a third-party CPaaS. That architectural difference produces three operational outcomes that third-party BCID partner stacks typically cannot match.<\/p>\n<p><strong>Carrier-level branded caller ID issuance.<\/strong> Plura issues a branded caller ID directly through its FCC-licensed carrier. Calls present with the company\u2019s name and the reason for the call, and STIR\/SHAKEN authentication runs on every outbound call at origination. Spam-label remediation is performed at the carrier level, not routed through an intermediary. Plura\u2019s AI also communicates with Apple\u2019s iOS 26 call-screening layer, so calls that would otherwise be intercepted can present a recognizable identity to the recipient.<\/p>\n<p><strong>Stateful conversation memory across channels.<\/strong> Plura\u2019s AI Voice, AI SMS, AI RCS (Rich Communication Services), and AI Webchat all share a Stateful Conversation Database. Every interaction is keyed to the same customer token, so a contact who received an SMS at 9 a.m. is the same contact when the voice call arrives at noon. No re-introduction and no repeated qualification. The context the AI holds on the call is the same context it held in the text thread.<\/p>\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>Compliance support infrastructure.<\/strong> Plura supports customer compliance with SOC 2, HIPAA, ISO certification, GDPR, SHAKEN\/STIR caller ID verification, TCPA compliance, and DNC compliance.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup> Every outbound contact is checked against federal and state DNC registries in real time before dial. Consent records are timestamped and immutable. Quiet-hours rules enforce automatically through time-zone detection. Plura provides the infrastructure, and customers remain responsible for their own compliance obligations and certifications.<\/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<p>For high-volume operators running 500 or more daily interactions, the economics of owning the carrier stack versus renting it through a BCID partner chain are material. The per-call wrapper cost that CPaaS resellers add compounds at scale. Plura\u2019s total cost of ownership of $300,000 to $700,000 per year replaces traditional contact-center economics of $4 million to $7 million on equivalent volume.<\/p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/plura.ai\/pricing\"><strong>Model the economics of Plura\u2019s carrier stack against your current CPaaS wrapper costs<\/strong><\/a> to quantify the delta.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is a BCID authorized partner?<\/h3>\n<p>A BCID authorized partner is an entity certified by CTIA to perform one or more functions within the Branded Calling ID ecosystem: signing, vetting, or onboarding. Authorized partners are contracted and audited against CTIA requirements. Operators work with one or more partner types depending on their infrastructure model. An FCC-licensed carrier that performs these functions natively can reduce the need for separate partner contracts.<\/p>\n<h3>How does BCID differ from STIR\/SHAKEN?<\/h3>\n<p>STIR\/SHAKEN is the FCC-mandated caller ID authentication framework that verifies a call originated from a legitimate source and assigns an attestation level (A, B, or C) based on how much the originating provider knows about the caller. BCID builds on top of STIR\/SHAKEN by attaching rich brand data, including name, logo, and call reason, to the authenticated call signal. STIR\/SHAKEN answers \u201cis this call legitimate?\u201d BCID answers \u201cwho is calling and why?\u201d Both layers work together in a complete branded calling deployment.<\/p>\n<h3>What is the difference between a signing agent and a vetting agent in BCID?<\/h3>\n<p>See the \u201cBCID Signing Agent vs. Vetting Agent\u201d section above for a detailed explanation of how signing agents operate at the cryptographic layer versus vetting agents at the identity layer, and why operators should evaluate each role independently.<\/p>\n<h3>Can Plura replace the BCID partner stack entirely?<\/h3>\n<p>Yes. As detailed in the \u201cPlura\u2019s Direct Carrier Path for Branded Calling\u201d section, Plura\u2019s FCC-licensed carrier status eliminates the need for separate signing, vetting, and onboarding agent contracts for operators who run voice through Plura\u2019s infrastructure. Operators with existing BCID partner agreements should evaluate the cost and compliance implications of consolidating onto a single carrier stack. Consult qualified counsel on any contractual obligations before making infrastructure changes.<\/p>\n<h3>What compliance frameworks does Plura support for branded calling deployments?<\/h3>\n<p>Plura supports customer compliance with SOC 2, HIPAA, ISO certification, GDPR, SHAKEN\/STIR caller ID verification, TCPA compliance, and DNC compliance. Real-time DNC scrubbing checks every outbound number before dial. Consent records are timestamped and immutable. Quiet-hours rules enforce automatically through time-zone detection. STIR\/SHAKEN authentication runs on every outbound voice call. Plura provides the infrastructure layer, and customers remain responsible for their own compliance obligations, certifications, and the claims they make to their end users. Operators should consult qualified counsel regarding their specific regulatory requirements.<\/p>\n<div data-type=\"horizontalRule\">\n<hr>\n<\/div>\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>Learn how BCID authorized partners work and how Plura&#8217;s direct carrier path delivers branded caller ID with compliance support. See how it compares.<\/p>\n","protected":false},"author":106,"featured_media":179,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-180","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\/180","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"}],"author":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/users\/106"}],"replies":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/comments?post=180"}],"version-history":[{"count":0,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/180\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/179"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}