{"id":491,"date":"2026-06-11T05:14:44","date_gmt":"2026-06-11T05:14:44","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/branded-caller-id-healthcare-examples"},"modified":"2026-06-11T05:14:44","modified_gmt":"2026-06-11T05:14:44","slug":"branded-caller-id-healthcare-examples","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/branded-caller-id-healthcare-examples","title":{"rendered":"Branded Caller ID Examples for Healthcare Outreach"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI<\/em><\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>\n<p>Branded caller ID replaces raw phone numbers with recognizable organization names, departments, and call reasons at the carrier level, which increases answer rates for healthcare outreach.<\/p>\n<\/li>\n<li>\n<p>Department-specific displays such as &#8220;City Medical Group &#8211; Scheduling&#8221; or &#8220;City Medical Group &#8211; Clinical&#8221; help patients quickly identify the purpose of the call without revealing protected health information.<\/p>\n<\/li>\n<li>\n<p>Plura AI issues branded caller ID through its own FCC-licensed carrier with STIR\/SHAKEN authentication, which supports A-level attestation and spam label remediation at origination instead of through third-party resellers.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup><\/p>\n<\/li>\n<li>\n<p>Healthcare organizations can support HIPAA-aligned practices by using only generic, non-clinical language in call-reason fields and keeping text to two or three words.<\/p>\n<\/li>\n<li>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.plura.ai\/plura-webchat\"><strong>Schedule a live demo with Plura<\/strong><\/a> to configure branded caller ID templates and track improvements in answer rates, no-shows, and compliance for your patient outreach programs.<\/p>\n<\/li>\n<\/ul>\n<h2>How Branded Caller ID Works in Healthcare<\/h2>\n<p>Branded caller ID in healthcare is a carrier-level feature that replaces a raw phone number on a patient&#8217;s handset with a recognizable organization name, department label, and call reason before the call is answered. <a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/www.plura.ai\/industries\/healthcare\">Plura AI<\/a> issues these identities directly through its own FCC-licensed carrier, so the display is set at origination instead of being added later through a third-party reseller. The result is a call that reads &#8220;City Medical Group &#8211; Scheduling&#8221; instead of an unfamiliar ten-digit number that <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.pewresearch.org\/short-reads\/2020\/12\/14\/most-americans-dont-answer-cellphone-calls-from-unknown-numbers\">80% of U.S. adults say they would not answer<\/a>.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<h2>12 Branded Caller ID Examples by Department<\/h2>\n<p>The table below covers twelve common patient outreach scenarios across six departments. Every name field follows an &#8220;Organization &#8211; Department&#8221; format, and call reason text uses only generic, non-clinical language. The table demonstrates how to structure the branded name, the call reason, and notes on HIPAA-aligned constraints for each scenario. Organizations should consult qualified counsel before finalizing any call reason text to confirm alignment with applicable privacy frameworks, including HIPAA (45 CFR Parts 160, 162, and 164).<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup><\/p>\n<table style=\"min-width: 100px\">\n<colgroup>\n<col style=\"min-width: 25px\">\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>Scenario<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Branded Name<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Call Reason<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Logo \/ Notes<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>New patient appointment booking<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Scheduling<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Appointment Request<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Logo supported on RCS-enabled handsets, no clinical detail in reason field<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Appointment reminder (24-hour)<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Scheduling<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Appt Reminder<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Example format displaying as &#8220;Main Street Pediatrics, Appt Reminder&#8221;<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Appointment reschedule outreach<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Scheduling<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Scheduling Follow-Up<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Triggered after a missed or cancelled slot, no diagnosis language<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Lab results notification<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Clinical<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Results Ready<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Reason field must not name the test or result, consult counsel<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Referral coordination<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Clinical<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Care Coordination<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Used when routing patients to specialist networks<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Prescription ready notification<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Pharmacy<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Rx Ready<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>No medication name in reason field<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Prescription refill reminder<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Pharmacy<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Refill Reminder<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Triggered by refill eligibility window, not diagnosis<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Balance due notification<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Billing<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Billing Notice<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>No balance amount or service description in reason field<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Insurance verification follow-up<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Billing<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Insurance Follow-Up<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Outbound only, no coverage detail in display<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Chronic care check-in<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Care Mgmt<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Care Check-In<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Used for population health and care management programs<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Post-discharge follow-up<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Care Mgmt<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Follow-Up Call<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Triggered within 48-72 hours of discharge, no diagnosis in display<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Patient satisfaction survey<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>City Medical Group &#8211; Patient Exp<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Feedback Request<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Separate display from clinical departments to avoid confusion<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.plura.ai\/plura-webchat\"><strong>See how these templates are configured for your departments<\/strong><\/a> in a live demo with Plura&#8217;s FCC-licensed carrier infrastructure.<\/p>\n<p>The following five scenarios represent the highest call volumes in many healthcare contact centers. Each one shows how branded caller ID addresses a specific patient communication challenge.<\/p>\n<h2>Five High-Volume Healthcare Use Cases in Detail<\/h2>\n<h3>Appointment Reminders<\/h3>\n<p>Appointment reminders are the single highest-volume outbound use case in most health systems. A display such as &#8220;City Medical Group &#8211; Scheduling \/ Appt Reminder&#8221; gives the patient immediate context before they decide to answer. Branded caller ID combined with AI-driven outreach cadences can reduce no-shows and keep schedules tighter.<\/p>\n<h3>Lab Results Notification<\/h3>\n<p>Lab result calls carry high patient anxiety, so clear identity matters. A display reading &#8220;City Medical Group &#8211; Clinical \/ Results Ready&#8221; signals that the call is expected and legitimate without disclosing any clinical detail in the caller ID field itself. The conversation that follows, handled by Plura&#8217;s AI Voice agent, can route the patient to a live clinician when the workflow requires it.<\/p>\n<h3>Pharmacy Outreach<\/h3>\n<p>Prescription ready and refill reminder calls are frequently abandoned when they display as unknown numbers. A separate pharmacy display such as &#8220;City Medical Group &#8211; Pharmacy&#8221; distinguishes these calls from clinical or billing contacts and reduces patient confusion about the call&#8217;s purpose.<\/p>\n<h3>Billing and Insurance Follow-Up<\/h3>\n<p>Billing calls are among the most likely to be screened or ignored. A &#8220;City Medical Group &#8211; Billing \/ Billing Notice&#8221; display establishes organizational identity without including any account or balance detail in the reason field, which sets a clear boundary for this display layer. Organizations should confirm the exact language with qualified counsel.<\/p>\n<h3>Post-Discharge Care Coordination<\/h3>\n<p>Post-discharge follow-up calls are time-sensitive and closely tied to readmission metrics. A display such as &#8220;City Medical Group &#8211; Care Mgmt \/ Follow-Up Call&#8221; within 48 to 72 hours of discharge signals continuity of care. TNS research found that 78% of adults are more willing to answer a branded call from a company they recognize, and a healthcare organization piloting TNS Enterprise Branded Calling reported a 41% increase in answer rates driven by enriched call data.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<h2>HIPAA-Aligned Call-Reason Rules<\/h2>\n<p>HIPAA (the Health Insurance Portability and Accountability Act, codified at 45 CFR Parts 160, 162, and 164) describes how protected health information (PHI) can be used and disclosed. The call reason field in a branded caller ID display is visible to anyone who sees the patient&#8217;s handset before the call is answered. Organizations should consult qualified legal counsel to determine what, if any, information is appropriate to include in that field under their specific compliance obligations.<\/p>\n<p>The following principles reflect common practice among healthcare contact centers, but they are not legal advice:<\/p>\n<ul>\n<li>\n<p>Use generic department or function labels (&#8220;Scheduling,&#8221; &#8220;Billing,&#8221; &#8220;Pharmacy&#8221;) rather than condition-specific or procedure-specific language. This keeps the display focused on the administrative purpose of the call instead of the patient&#8217;s health status.<\/p>\n<\/li>\n<li>\n<p>Within that generic framing, do not include test names, medication names, diagnosis codes, or any information that could identify a health condition in the reason field. Even seemingly routine terms can reveal protected information.<\/p>\n<\/li>\n<li>\n<p>Keep reason text to two to three words. Shorter text reduces the risk of inadvertent disclosure and increases the chance that the full phrase displays consistently across handsets.<\/p>\n<\/li>\n<li>\n<p>Maintain separate branded displays for clinical, administrative, and billing departments so patients can distinguish the call type without the display revealing clinical detail. This separation also helps patients prioritize which calls to answer first.<\/p>\n<\/li>\n<\/ul>\n<p>Plura supports HIPAA-aligned configurations with end-to-end encryption, access controls, and audit logging for protected health information. Customers are responsible for their own HIPAA compliance obligations and should engage qualified counsel before finalizing any call reason text.<\/p>\n<h2>Carrier-Level Spam Remediation and STIR\/SHAKEN Authentication<\/h2>\n<p>Most AI voice platforms cannot issue branded caller ID at the carrier level because they route calls through a third-party Communications Platform as a Service (CPaaS) such as Twilio.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"4\">4<\/sup> They inherit that carrier&#8217;s caller ID reputation, not their own. Plura is its own FCC-licensed audio bridging carrier, so branded caller ID is issued at origination instead of being added through a reseller, and the display is anchored to Plura&#8217;s carrier identity rather than a shared CPaaS pool.<\/p>\n<p>STIR\/SHAKEN (Secure Telephone Identity Revisited \/ Signature-based Handling of Asserted information using toKENs) is the FCC-mandated caller ID authentication framework implemented under the TRACED Act. Every outbound call on Plura&#8217;s carrier receives STIR\/SHAKEN authentication at origination. The FCC has proposed requiring terminating providers to transmit verified caller name or other caller identity information for presentation on a consumer&#8217;s handset whenever they transmit an indication that a call has received an A-level attestation, which is the highest attestation level and requires the originating carrier to have registered the calling number. Plura&#8217;s carrier-level registration supports A-level attestation on eligible numbers.<\/p>\n<p>Spam label remediation operates at the same layer. When a number is flagged by a downstream carrier or analytics provider, Plura addresses the flag through its carrier identity infrastructure instead of relying on a third-party remediation service. TransUnion data cited in the FCC rulemaking record indicates that customers are up to 105% more likely to answer a branded call compared to an unbranded one, which reflects the combined effect of identity display and spam label removal.<sup data-disclaimer-id=\"24\" data-disclaimer-index=\"3\">3<\/sup><\/p>\n<p>Plura&#8217;s AI also communicates with Apple&#8217;s iOS 26 call-screening layer, so calls that would otherwise be intercepted before ringing through can present a recognizable identity to the recipient.<\/p>\n<p>Once branded caller ID is live across these technical layers, the next step is confirming that it delivers the operational improvements your contact center expects.<\/p>\n<h2>Measuring Success of Branded Caller ID<\/h2>\n<p>Branded caller ID affects three operational layers: whether patients answer the call, whether they show up for the appointment, and whether outreach workflows support regulatory compliance. Contact center and compliance leaders should track metrics in each category to isolate the impact of branded caller ID from other workflow changes.<\/p>\n<p><strong>Answer rate.<\/strong> Track baseline answer rate before deployment versus post-deployment answer rate by department and call type. Segment by inbound versus outbound and by time of day to separate the branded caller ID effect from dialing-window changes. The 41% answer rate improvement cited earlier illustrates the potential scale of impact, so segment your own data by department and call type to understand where the gains occur.<\/p>\n<p><strong>No-show reduction.<\/strong> Track appointment no-show rates before and after deploying branded outreach cadences. Branded caller ID combined with structured outreach sequences can reduce no-shows. Segment by appointment type and department to identify where branded caller ID has the highest marginal impact.<\/p>\n<p><strong>Compliance metrics.<\/strong> Track DNC compliance rate, consent record completeness, quiet-hours adherence, and audit log completeness. Plura&#8217;s compliance engine supports TCPA-aligned controls, DNC handling, and HIPAA-aligned data handling on outbound contacts, with one-click audit-ready exports for legal review or carrier requirements.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup><\/p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.plura.ai\/plura-webchat\"><strong>Walk through Plura&#8217;s reporting dashboard<\/strong><\/a> in a live demo to see how these metrics are surfaced for healthcare contact centers.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Healthcare Branded Caller ID Setup Timelines<\/h3>\n<p>Setup timelines depend on the number of departments, the complexity of the outreach workflows, and how quickly the organization confirms its branded name and call reason text with internal compliance and legal teams. A straightforward deployment covering two to three departments with pre-approved reason text can go live in days. A multi-department rollout with custom workflow logic for appointment reminders, post-discharge follow-up, and billing typically runs one to two months from kickoff to full go-live. Plura&#8217;s onboarding sequence includes a discovery audit, a workflow mockup reviewed with the customer, an engineering build, a pilot test on a subset of real calls, and then full deployment.<\/p>\n<h3>Prerequisites for Deploying Branded Caller ID<\/h3>\n<p>The core prerequisites include a confirmed branded display name approved by the organization&#8217;s legal and compliance team, a defined list of departments and call reason text reviewed against applicable privacy frameworks, and registered phone numbers that can receive A-level STIR\/SHAKEN attestation. Organizations also need an active Business Associate Agreement (BAA) in place with any vendor handling protected health information in the call flow. Plura supports HIPAA-aligned configurations with end-to-end encryption and audit logging. Customers are responsible for their own BAA obligations and compliance determinations.<\/p>\n<h3>Department-Specific Displays on a Single Phone System<\/h3>\n<p>Branded caller ID can display different names for different departments on the same phone system. Plura issues branded caller ID at the carrier level on a per-number basis, so each department can have its own registered display name and call reason. A scheduling line can display &#8220;City Medical Group &#8211; Scheduling \/ Appt Reminder&#8221; while a billing line displays &#8220;City Medical Group &#8211; Billing \/ Billing Notice&#8221; from the same organization. This separation is operationally useful because it lets patients distinguish the call type before answering and keeps clinical, administrative, and billing identities distinct in the caller ID layer.<\/p>\n<h3>Carrier and Handset Support for Branded Caller ID<\/h3>\n<p>Branded name and call reason display depends on the terminating carrier&#8217;s support for STIR\/SHAKEN and Rich Call Data (RCD) transmission. The major U.S. wireless carriers support branded calling display for calls that receive A-level attestation from an originating carrier registered with the carrier&#8217;s identity framework. Logo display requires RCS (Rich Communication Services) support on the recipient&#8217;s handset and carrier. Not all handsets or carriers support logo display at this time. Plura&#8217;s carrier-level registration supports A-level attestation on eligible numbers, which is the prerequisite for branded display on supported networks.<\/p>\n<h3>Spam Label Remediation for Healthcare Outreach Numbers<\/h3>\n<p>Spam label remediation is handled through Plura&#8217;s carrier identity infrastructure directly. When a number receives a spam or scam-likely label from a downstream analytics provider or terminating carrier, Plura addresses the flag at the origination layer instead of routing a remediation request through a third-party service. This structure differs from platforms that rent carrier access from Twilio or another CPaaS and inherit a shared caller ID reputation pool. STIR\/SHAKEN authentication on every outbound call also signals legitimate origination to the terminating carrier, which is one of the primary inputs downstream analytics providers use when assigning call labels.<\/p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.plura.ai\/plura-webchat\"><strong>See how Plura&#8217;s carrier infrastructure handles branded caller ID and spam remediation<\/strong><\/a> in a live demo focused on healthcare patient outreach at scale.<\/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>See branded caller ID examples built for healthcare. Plura issues STIR\/SHAKEN-authenticated display names at the carrier level to raise answer rates.<\/p>\n","protected":false},"author":106,"featured_media":490,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-491","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\/491","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=491"}],"version-history":[{"count":0,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/490"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}