{"id":8438,"date":"2026-03-26T03:19:53","date_gmt":"2026-03-26T03:19:53","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/delivery-receipt\/"},"modified":"2026-03-26T03:19:53","modified_gmt":"2026-03-26T03:19:53","slug":"delivery-receipt","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/delivery-receipt\/","title":{"rendered":"Delivery Receipt: What It Is, Key Features, Benefits, Use Cases, and How It Fits in SMS Marketing"},"content":{"rendered":"\n<p>In <strong>Direct &amp; Retention Marketing<\/strong>, every message you send should have a measurable outcome\u2014especially in <strong>SMS Marketing<\/strong>, where you pay per message and customers expect timely, relevant communications. A <strong>Delivery Receipt<\/strong> is the mechanism that confirms whether an SMS message reached the recipient\u2019s device (or at least the recipient\u2019s network\/device boundary, depending on the route and carrier).<\/p>\n\n\n\n<p>Understanding <strong>Delivery Receipt<\/strong> data helps teams separate \u201csent\u201d from \u201cdelivered,\u201d troubleshoot deliverability issues, control costs, and design smarter automations. In modern <strong>Direct &amp; Retention Marketing<\/strong> strategy, it\u2019s also a foundation for accurate reporting, attribution, and customer experience decisions\u2014because a campaign can\u2019t drive results if it never arrives.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Is Delivery Receipt?<\/h2>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> is a delivery status confirmation generated after an SMS message is submitted to a messaging provider and then processed by downstream networks. In practical terms, it\u2019s the feedback signal that tells you whether the message was:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>delivered successfully,<\/li>\n<li>failed (and often why),<\/li>\n<li>still pending, or<\/li>\n<li>expired\/timed out.<\/li>\n<\/ul>\n\n\n\n<p>The core concept is simple: <strong>Delivery Receipt<\/strong> data bridges the gap between \u201cwe sent an SMS\u201d and \u201cthe SMS reached the destination.\u201d In <strong>SMS Marketing<\/strong>, this is critical because sending is not the same as delivering\u2014carriers can block messages, numbers can be invalid, devices can be offline, and routing can vary.<\/p>\n\n\n\n<p>From a business standpoint, <strong>Delivery Receipt<\/strong> status becomes a truth source for operational decisions in <strong>Direct &amp; Retention Marketing<\/strong>\u2014for example, whether to retry a message, switch channels, suppress future sends, or trigger a follow-up sequence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Delivery Receipt Matters in Direct &amp; Retention Marketing<\/h2>\n\n\n\n<p>In <strong>Direct &amp; Retention Marketing<\/strong>, speed and reliability often determine conversion. A <strong>Delivery Receipt<\/strong> directly influences outcomes because it tells you whether your message had a chance to be seen.<\/p>\n\n\n\n<p>Key reasons it matters:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Budget accountability:<\/strong> In <strong>SMS Marketing<\/strong>, cost is tied to message volume. <strong>Delivery Receipt<\/strong> data helps quantify waste from undelivered sends and identify opportunities to reduce spend.<\/li>\n<li><strong>Campaign accuracy:<\/strong> Without <strong>Delivery Receipt<\/strong> status, \u201cmessage sent\u201d can inflate success metrics and mask deliverability problems.<\/li>\n<li><strong>Customer experience:<\/strong> Repeatedly texting unreachable or invalid numbers increases annoyance, risks complaints, and can harm brand trust\u2014especially in retention workflows.<\/li>\n<li><strong>Competitive advantage:<\/strong> Teams that monitor <strong>Delivery Receipt<\/strong> patterns can improve routing, list hygiene, and timing, resulting in higher effective reach than competitors using \u201csend-and-hope\u201d tactics.<\/li>\n<\/ul>\n\n\n\n<p>Used well, <strong>Delivery Receipt<\/strong> insights turn <strong>Direct &amp; Retention Marketing<\/strong> from a broadcast approach into a controlled system with feedback loops.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Delivery Receipt Works<\/h2>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> is easiest to understand as a workflow that spans your marketing stack and telecom networks.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Input \/ Trigger<\/strong>\n   &#8211; A customer action (signup, purchase, abandoned cart), a scheduled campaign, or an automated journey triggers an SMS send in your <strong>SMS Marketing<\/strong> platform.\n   &#8211; The message includes key metadata such as destination number, sender identity, and a campaign or customer identifier for reporting.<\/p>\n<\/li>\n<li>\n<p><strong>Processing<\/strong>\n   &#8211; Your messaging provider accepts the message and attempts delivery through one or more routes (often via carrier connections or aggregators).\n   &#8211; The carrier\/network validates the number, applies filtering policies, and attempts to deliver to the handset.<\/p>\n<\/li>\n<li>\n<p><strong>Execution<\/strong>\n   &#8211; Delivery is attempted; if the device is unavailable, the network may keep retrying for a period.\n   &#8211; If delivery succeeds, fails, or times out, the downstream system produces a status update.<\/p>\n<\/li>\n<li>\n<p><strong>Output \/ Outcome<\/strong>\n   &#8211; The <strong>Delivery Receipt<\/strong> is returned to your provider and then surfaced to your systems (dashboard, logs, or callbacks).\n   &#8211; Your <strong>Direct &amp; Retention Marketing<\/strong> automations can use that status to update profiles, trigger next steps, and inform reporting.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p>Important nuance: a <strong>Delivery Receipt<\/strong> typically indicates <em>technical delivery<\/em> to the device or network endpoint\u2014not that the customer read or acted on the message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Key Components of Delivery Receipt<\/h2>\n\n\n\n<p>To operationalize <strong>Delivery Receipt<\/strong> in <strong>SMS Marketing<\/strong>, you need more than a status label. The most useful implementations include these components:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Status codes and reason codes:<\/strong> Delivered, failed, pending, expired, rejected\u2014plus a reason such as \u201cinvalid number\u201d or \u201cblocked by carrier.\u201d<\/li>\n<li><strong>Timestamps:<\/strong> When the message was submitted, when delivery was attempted, and when final status was confirmed. This enables latency analysis.<\/li>\n<li><strong>Message identifiers:<\/strong> A unique message ID that can be joined to campaign, customer, and channel data in <strong>Direct &amp; Retention Marketing<\/strong> reporting.<\/li>\n<li><strong>Recipient and route metadata (where available):<\/strong> Country, carrier, or route type to identify systematic issues.<\/li>\n<li><strong>Data pipeline and storage:<\/strong> Logging that preserves <strong>Delivery Receipt<\/strong> events for auditing, analytics, and troubleshooting.<\/li>\n<li><strong>Governance and ownership:<\/strong> Clear responsibility between marketing ops, engineering, and compliance for monitoring delivery performance and responding to anomalies.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Types of Delivery Receipt<\/h2>\n\n\n\n<p>\u201cTypes\u201d of <strong>Delivery Receipt<\/strong> are less about formal categories and more about practical distinctions that affect interpretation:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Final vs. interim status<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Interim states<\/strong> may show that a message is accepted and in progress.<\/li>\n<li><strong>Final states<\/strong> indicate delivered, failed, or expired. Final states are what you want for clean measurement in <strong>Direct &amp; Retention Marketing<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Success vs. failure (and \u201cunknown\u201d)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Delivered:<\/strong> The network reports successful delivery.<\/li>\n<li><strong>Failed:<\/strong> Delivery could not be completed (with a reason when available).<\/li>\n<li><strong>Unknown\/undetermined:<\/strong> Some routes provide limited visibility, and you may not get a definitive final signal.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Device-delivered vs. network-acknowledged<\/h3>\n\n\n\n<p>Depending on carrier behavior and routing, a <strong>Delivery Receipt<\/strong> may indicate delivery to the handset or only acknowledgment by a network component. This affects how confidently you can treat \u201cdelivered\u201d as \u201cseen\u201d in <strong>SMS Marketing<\/strong> performance analysis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Real-World Examples of Delivery Receipt<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Example 1: Abandoned cart SMS with fallback<\/h3>\n\n\n\n<p>A retailer runs an abandoned cart journey in <strong>Direct &amp; Retention Marketing<\/strong>. If the first SMS reminder returns a failed <strong>Delivery Receipt<\/strong> with an \u201cinvalid number\u201d reason, the system:\n&#8211; suppresses future SMS to that profile,\n&#8211; sends an email instead,\n&#8211; flags the account for number re-collection at next login.<\/p>\n\n\n\n<p>This prevents repeated spend on unreachable numbers and protects the customer experience.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example 2: OTP or critical account alert timing analysis<\/h3>\n\n\n\n<p>A fintech uses <strong>SMS Marketing<\/strong> for security alerts. They track <strong>Delivery Receipt<\/strong> latency (submit-to-delivered time). If a carrier shows consistent delays during peak hours, they:\n&#8211; adjust send throttling,\n&#8211; add routing redundancy via an alternate path (through their provider),\n&#8211; update SLAs and monitoring alerts.<\/p>\n\n\n\n<p>The result is fewer timeouts and fewer support tickets tied to delayed messages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example 3: Win-back campaign deliverability cleanup<\/h3>\n\n\n\n<p>A subscription business runs a win-back campaign and sees strong \u201csent\u201d volume but weak response. <strong>Delivery Receipt<\/strong> reporting reveals that a large segment is expiring (devices unreachable) or failing (numbers recycled). The team improves list hygiene and reduces send volume\u2014leading to higher effective reach and more accurate ROI in <strong>Direct &amp; Retention Marketing<\/strong> reporting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Benefits of Using Delivery Receipt<\/h2>\n\n\n\n<p>Using <strong>Delivery Receipt<\/strong> data intentionally can improve both performance and operational efficiency:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Better measurement integrity:<\/strong> You can calculate delivery rate and separate deliverability from creative\/offer performance in <strong>SMS Marketing<\/strong>.<\/li>\n<li><strong>Lower wasted spend:<\/strong> Suppressing undeliverable numbers reduces repeated failed sends.<\/li>\n<li><strong>Smarter automation:<\/strong> Trigger retries only when appropriate, or switch to another channel when delivery fails.<\/li>\n<li><strong>Faster troubleshooting:<\/strong> When campaigns underperform, <strong>Delivery Receipt<\/strong> patterns often reveal whether the issue is content, list quality, or carrier filtering.<\/li>\n<li><strong>Improved customer experience:<\/strong> Fewer duplicate texts, fewer late-arriving messages, and fewer messages to unreachable recipients support retention goals in <strong>Direct &amp; Retention Marketing<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Challenges of Delivery Receipt<\/h2>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> is valuable, but it\u2019s not perfect. Common challenges include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Not the same as \u201cread\u201d:<\/strong> Delivery does not guarantee attention, comprehension, or engagement. For <strong>Direct &amp; Retention Marketing<\/strong> analysis, combine delivery with downstream actions.<\/li>\n<li><strong>Inconsistent granularity:<\/strong> Reason codes and status detail vary by carrier, geography, and route.<\/li>\n<li><strong>Latency and timeouts:<\/strong> Messages can sit in retry windows before expiring, complicating real-time decisioning.<\/li>\n<li><strong>Filtering and blocking opacity:<\/strong> Carriers may block messages with limited explanation, especially when policies change.<\/li>\n<li><strong>Data integration gaps:<\/strong> If <strong>Delivery Receipt<\/strong> events aren\u2019t reliably joined to campaign IDs and customer profiles, measurement becomes fragmented.<\/li>\n<li><strong>Edge cases:<\/strong> Number recycling, roaming behavior, and device state can produce confusing patterns over time.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices for Delivery Receipt<\/h2>\n\n\n\n<p>To get reliable value from <strong>Delivery Receipt<\/strong> in <strong>SMS Marketing<\/strong> and <strong>Direct &amp; Retention Marketing<\/strong>, focus on these practices:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Treat delivery as a required metric, not a nice-to-have:<\/strong> Report on delivered volume, not only sent volume.<\/li>\n<li><strong>Build a suppression strategy:<\/strong> Automatically suppress numbers with repeated failures (especially invalid or permanently unreachable results).<\/li>\n<li><strong>Use delivery-aware automations:<\/strong><\/li>\n<li>retry only when failure reason suggests it may succeed later,<\/li>\n<li>avoid immediate repeats that can create duplicates if delivery status arrives late.<\/li>\n<li><strong>Monitor by segment and route:<\/strong> Break down <strong>Delivery Receipt<\/strong> rates by country, carrier (if available), campaign type, and send time.<\/li>\n<li><strong>Set latency thresholds:<\/strong> Alert when delivery time exceeds your acceptable window for the use case (promotions vs. time-sensitive alerts).<\/li>\n<li><strong>Keep list hygiene proactive:<\/strong> Validate collection flows, confirm opt-in, and regularly clean obvious invalid formats.<\/li>\n<li><strong>Align teams on definitions:<\/strong> Ensure marketing, analytics, and engineering agree on what \u201cdelivered,\u201d \u201cfailed,\u201d and \u201cexpired\u201d mean in dashboards.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Tools Used for Delivery Receipt<\/h2>\n\n\n\n<p><strong>Delivery Receipt<\/strong> is operationalized through systems, not a single tool. Common tool categories in <strong>Direct &amp; Retention Marketing<\/strong> and <strong>SMS Marketing<\/strong> include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Messaging providers and gateways:<\/strong> The core layer that sends messages and returns <strong>Delivery Receipt<\/strong> events and reason codes.<\/li>\n<li><strong>Marketing automation platforms:<\/strong> Use delivery status to branch journeys, suppress contacts, and coordinate multi-step sequences.<\/li>\n<li><strong>CRM and customer data platforms:<\/strong> Store delivery outcomes as customer-level attributes (e.g., last delivery status, failure count).<\/li>\n<li><strong>Analytics and BI dashboards:<\/strong> Combine <strong>Delivery Receipt<\/strong> data with campaign metadata and conversion outcomes for performance reporting.<\/li>\n<li><strong>Data pipelines and warehouses:<\/strong> Centralize event logs so analysts can model deliverability trends over time.<\/li>\n<li><strong>Monitoring and incident tooling:<\/strong> Alerts for sudden drops in delivered rate, spikes in failures, or abnormal latency.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Metrics Related to Delivery Receipt<\/h2>\n\n\n\n<p>To make <strong>Delivery Receipt<\/strong> actionable, track metrics that connect delivery quality to business impact:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Delivery rate:<\/strong> Delivered \/ sent (or delivered \/ accepted, depending on your reporting model).<\/li>\n<li><strong>Failure rate:<\/strong> Failed \/ sent, ideally segmented by reason (invalid, blocked, unreachable, expired).<\/li>\n<li><strong>Expiry rate:<\/strong> Share of messages that time out before delivery\u2014often a sign of unreachable devices or timing issues.<\/li>\n<li><strong>Delivery latency:<\/strong> Time from submission to delivered. Critical for time-sensitive <strong>SMS Marketing<\/strong> use cases.<\/li>\n<li><strong>Cost per delivered message:<\/strong> Spend divided by delivered count (more meaningful than cost per send).<\/li>\n<li><strong>Reachable audience size:<\/strong> Number of contacts with recent successful <strong>Delivery Receipt<\/strong> outcomes (useful for retention forecasting).<\/li>\n<li><strong>Downstream conversion on delivered messages:<\/strong> Conversions \/ delivered, to separate deliverability from offer performance in <strong>Direct &amp; Retention Marketing<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Future Trends of Delivery Receipt<\/h2>\n\n\n\n<p>Several trends are shaping how <strong>Delivery Receipt<\/strong> is used in <strong>Direct &amp; Retention Marketing<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>More automation in routing and optimization:<\/strong> Systems increasingly adjust routes, throttling, and send windows based on delivery performance patterns.<\/li>\n<li><strong>AI-assisted anomaly detection:<\/strong> Models can flag unusual <strong>Delivery Receipt<\/strong> failure spikes, predict deliverability risk by segment, and recommend mitigations.<\/li>\n<li><strong>Stronger identity and trust signals:<\/strong> As ecosystems push for verified sender identities, delivery outcomes may become more stable for compliant programs.<\/li>\n<li><strong>Richer messaging ecosystems:<\/strong> As messaging options evolve, delivery feedback may include more context\u2014though SMS will remain a critical baseline channel.<\/li>\n<li><strong>Privacy and measurement tightening:<\/strong> Marketers will rely more on first-party event logs (including <strong>Delivery Receipt<\/strong> events) and less on ambiguous attribution methods.<\/li>\n<\/ul>\n\n\n\n<p>The net effect: <strong>Delivery Receipt<\/strong> will continue shifting from a technical detail to a core feedback signal that powers smarter retention systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Delivery Receipt vs Related Terms<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery Receipt vs Read receipt<\/h3>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> confirms technical delivery, while a <strong>read receipt<\/strong> indicates the recipient opened or read the message (where supported). In <strong>SMS Marketing<\/strong>, read receipts are generally not a standard capability, so delivery is often the highest-fidelity status available.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery Receipt vs Send confirmation (accepted\/submitted)<\/h3>\n\n\n\n<p>\u201cAccepted\u201d or \u201csubmitted\u201d typically means your provider received the message request. A <strong>Delivery Receipt<\/strong> reflects what happened after the provider handed the message off to networks and delivery was attempted.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery Receipt vs Click tracking<\/h3>\n\n\n\n<p>Click tracking measures engagement (tap\/click on a link). <strong>Delivery Receipt<\/strong> measures reachability. In <strong>Direct &amp; Retention Marketing<\/strong>, you need both to diagnose performance: low clicks could be an offer issue\u2014or simply low delivery.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who Should Learn Delivery Receipt<\/h2>\n\n\n\n<p><strong>Delivery Receipt<\/strong> knowledge pays off across roles:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Marketers:<\/strong> Plan campaigns using delivered volume and delivery-aware automations, improving <strong>Direct &amp; Retention Marketing<\/strong> outcomes.<\/li>\n<li><strong>Analysts:<\/strong> Build cleaner funnels by separating sent vs delivered vs engaged, improving <strong>SMS Marketing<\/strong> reporting integrity.<\/li>\n<li><strong>Agencies:<\/strong> Diagnose client performance quickly, proving where issues sit (list quality, content, routing, timing).<\/li>\n<li><strong>Business owners and founders:<\/strong> Control spend and improve customer experience with clearer operational levers.<\/li>\n<li><strong>Developers:<\/strong> Implement reliable event handling, data joins, and retries without causing duplicate messages or broken journeys.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Summary of Delivery Receipt<\/h2>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> is the status feedback that indicates whether an SMS message was delivered, failed, or expired. In <strong>Direct &amp; Retention Marketing<\/strong>, it supports accurate measurement, cost control, and automation decisions. In <strong>SMS Marketing<\/strong>, it\u2019s one of the most important signals for deliverability health\u2014helping teams distinguish between messages that were merely sent and messages that actually reached customers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions (FAQ)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) What does a Delivery Receipt actually confirm?<\/h3>\n\n\n\n<p>A <strong>Delivery Receipt<\/strong> confirms the outcome of delivery attempts\u2014typically that the SMS reached the recipient\u2019s device or the carrier\u2019s delivery endpoint. It does not guarantee the person read or acted on the message.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Why is Delivery Receipt data essential for SMS Marketing reporting?<\/h3>\n\n\n\n<p>Because \u201csent\u201d can be misleading. <strong>SMS Marketing<\/strong> performance should be evaluated on delivered volume and delivery rate; otherwise, you may attribute poor results to creative or offers when the real issue is deliverability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Can a message show \u201cdelivered\u201d but still not be seen?<\/h3>\n\n\n\n<p>Yes. The phone could be unattended, notifications muted, or the message overlooked. <strong>Delivery Receipt<\/strong> indicates delivery success, not attention or comprehension.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) How should I use Delivery Receipt failures in automations?<\/h3>\n\n\n\n<p>Use failures to suppress bad numbers, trigger alternative channels (like email), and decide whether to retry. Base retries on the failure reason and time sensitivity, so you don\u2019t create duplicates.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) What\u2019s the difference between \u201csubmitted\u201d and \u201cdelivered\u201d statuses?<\/h3>\n\n\n\n<p>\u201cSubmitted\u201d means your provider accepted the send request. \u201cDelivered\u201d (via <strong>Delivery Receipt<\/strong>) means the downstream network reported successful delivery.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) What is a good delivery rate benchmark?<\/h3>\n\n\n\n<p>It varies by country, carrier mix, use case, and list quality. Instead of chasing a universal benchmark, track trends over time and compare like-for-like segments within your <strong>Direct &amp; Retention Marketing<\/strong> program.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In **Direct &#038; Retention Marketing**, every message you send should have a measurable outcome\u2014especially in **SMS Marketing**, where you pay per message and customers expect timely, relevant communications. A **Delivery Receipt** is the mechanism that confirms whether an SMS message reached the recipient\u2019s device (or at least the recipient\u2019s network\/device boundary, depending on the route and carrier).<\/p>\n","protected":false},"author":10235,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1897],"tags":[],"class_list":["post-8438","post","type-post","status-publish","format-standard","hentry","category-sms-marketing"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8438","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/users\/10235"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/comments?post=8438"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8438\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=8438"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=8438"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=8438"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}