{"id":13118,"date":"2026-10-17T14:43:55","date_gmt":"2026-10-17T14:43:55","guid":{"rendered":"https:\/\/botsify.com\/blog\/?p=13118"},"modified":"2026-10-17T14:45:12","modified_gmt":"2026-10-17T14:45:12","slug":"ai-customer-support-metrics-beyond-deflection","status":"publish","type":"post","link":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/","title":{"rendered":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection"},"content":{"rendered":"<p>\u201cWe deflected 60% of tickets\u201d is the metric most teams lead with. It&#8217;s also the one most likely to hide a problem. Deflection measures volume, not quality. An AI agent can close conversations without solving customer issues, making performance look impressive while customer satisfaction quietly declines.<\/p>\n<p>That&#8217;s why tracking the right AI customer support metrics matters. Beyond ticket deflection, you need to understand whether customers receive accurate answers, how often they contact support again, when conversations require human assistance, and what each successful resolution costs.<\/p>\n<p>This guide explains which metrics to track, how to measure them, and how to build a reporting process that helps improve customer support rather than simply make automation look successful.<\/p>\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-support-analytics-dashboard.jpg\" alt=\"AI customer support metrics\" width=\"1942\" height=\"809\" \/><\/figure>\n<h2><\/h2>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title ez-toc-toggle\" style=\"cursor:pointer\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #fee22e;color:#fee22e\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #fee22e;color:#fee22e\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Why_deflection_alone_misleads\" >Why deflection alone misleads<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#The_8_AI_Customer_Support_Metrics_That_Actually_Matter\" >The 8 AI Customer Support Metrics That Actually Matter<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_1_CSAT_on_AI-handled_conversations\" >Metric 1: CSAT on AI-handled conversations<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_2_First_contact_resolution\" >Metric 2: First contact resolution<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_3_Escalation_rate_calibrated_not_minimized\" >Metric 3: Escalation rate, calibrated, not minimized<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_4_Coverage_by_category\" >Metric 4: Coverage by category<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_5_Time_to_resolution_AI_vs_human\" >Metric 5: Time to resolution (AI vs human)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_6_Cost_per_resolution\" >Metric 6: Cost per resolution<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Example_calculation\" >Example calculation<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_7_Transcript_quality_trend\" >Metric 7: Transcript quality trend<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metric_8_Knowledge_base_freshness\" >Metric 8: Knowledge base freshness<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_to_Build_an_AI_Customer_Support_Metrics_Dashboard\" >How to Build an AI Customer Support Metrics Dashboard<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Start_with_three_priorities\" >Start with three priorities<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Keep_the_setup_simple\" >Keep the setup simple<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Track_What_Matters_in_AI_Support\" >Track What Matters in AI Support<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_to_Set_Realistic_AI_Customer_Support_Metrics_Targets\" >How to Set Realistic AI Customer Support Metrics Targets<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Record_your_baseline\" >Record your baseline<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Review_progress_at_30_60_and_90_days\" >Review progress at 30, 60, and 90 days<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Common_Mistakes_When_Tracking_AI_Customer_Support_Metrics\" >Common Mistakes When Tracking AI Customer Support Metrics<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Metrics_that_can_be_misleading\" >Metrics that can be misleading<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Other_mistakes_to_avoid\" >Other mistakes to avoid<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_to_Review_AI_Customer_Support_Metrics_Regularly\" >How to Review AI Customer Support Metrics Regularly<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Weekly_review_30_minutes\" >Weekly review: 30 minutes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Monthly_performance_review\" >Monthly performance review<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Quarterly_review\" >Quarterly review<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_to_Report_AI_Customer_Support_Performance_to_Leadership\" >How to Report AI Customer Support Performance to Leadership<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Explain_what_the_numbers_mean\" >Explain what the numbers mean<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Address_common_leadership_questions\" >Address common leadership questions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Make_Your_AI_Support_Work_Better\" >Make Your AI Support Work Better<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#What_to_do_when_metrics_go_wrong\" >What to do when metrics go wrong<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Frequently_Asked_Questions_About_AI_Customer_Support_Metrics\" >Frequently Asked Questions About AI Customer Support Metrics<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#What_are_the_most_important_AI_customer_support_metrics\" >What are the most important AI customer support metrics?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_do_you_measure_CSAT_on_AI_conversations\" >How do you measure CSAT on AI conversations?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Should_AI_and_human_support_share_the_same_CSAT_score\" >Should AI and human support share the same CSAT score?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-35\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#What_is_a_good_AI_ticket_deflection_rate\" >What is a good AI ticket deflection rate?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-36\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_often_should_AI_support_metrics_be_reviewed\" >How often should AI support metrics be reviewed?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-37\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#What_should_you_do_when_AI_CSAT_is_low\" >What should you do when AI CSAT is low?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#How_long_does_it_take_to_establish_reliable_performance_metrics\" >How long does it take to establish reliable performance metrics?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Should_customer_support_teams_have_access_to_AI_performance_metrics\" >Should customer support teams have access to AI performance metrics?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-40\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#Final_thought\" >Final thought<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-41\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#AI_Agentic_Platform_For_Building_Portable_AI_Agents\" >AI Agentic Platform For Building Portable AI Agents<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 id=\"why-deflection-alone-misleads\"><span class=\"ez-toc-section\" id=\"Why_deflection_alone_misleads\"><\/span><strong>Why deflection alone misleads<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Deflection rate answers one question: how many conversations did the AI handle without a human? It does not answer:<\/p>\n<ul>\n<li>Did the customer get a correct answer?<\/li>\n<li>Are they satisfied?<\/li>\n<li>Did they contact you again about the same issue?<\/li>\n<li>Did the AI promise something a human has to fix later?<\/li>\n<\/ul>\n<p>A team can hit 70% deflection while quietly accumulating angry customers who stopped bothering to reply. That is worse than a lower deflection rate with happy customers.<\/p>\n<blockquote><p>Deflection tells you what the AI touched. It tells you nothing about whether the touch helped.<\/p><\/blockquote>\n<p>Before diving into metrics, it is worth being clear about what you are measuring: <a href=\"https:\/\/botsify.com\/blog\/customer-support-ai-agents-guide\/\">AI customer support agents<\/a> that answer questions, triage requests, and escalate complex issues, not just deflection counters.<\/p>\n<h2 id=\"the-metric-stack-that-actually-matters\"><span class=\"ez-toc-section\" id=\"The_8_AI_Customer_Support_Metrics_That_Actually_Matter\"><\/span>The 8 AI Customer Support Metrics That Actually Matter<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Here are the eight metrics worth tracking, in priority order:<\/p>\n<table>\n<colgroup>\n<col style=\"width: 25%;\" \/>\n<col style=\"width: 25%;\" \/>\n<col style=\"width: 25%;\" \/>\n<col style=\"width: 25%;\" \/> <\/colgroup>\n<thead>\n<tr class=\"header\">\n<th>#<\/th>\n<th>Metric<\/th>\n<th>What it tells you<\/th>\n<th>Target<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>1<\/td>\n<td>CSAT on AI-handled conversations<\/td>\n<td>Whether customers are satisfied<\/td>\n<td>4.2+\/5 or equivalent<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>2<\/td>\n<td>First contact resolution<\/td>\n<td>Whether the answer actually solved the problem<\/td>\n<td>60%+<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>3<\/td>\n<td>Escalation rate<\/td>\n<td>Whether routing is calibrated<\/td>\n<td>10\u201325%<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>4<\/td>\n<td>Repeat contact rate<\/td>\n<td>Whether the first answer stuck<\/td>\n<td>Under 15%<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>5<\/td>\n<td>First response time<\/td>\n<td>Speed across all hours<\/td>\n<td>Under 1 minute<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>6<\/td>\n<td>Resolution rate<\/td>\n<td>How much the AI handles end-to-end<\/td>\n<td>Varies by category<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>7<\/td>\n<td>Deflection<\/td>\n<td>Volume handled without humans<\/td>\n<td>Context metric only<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>8<\/td>\n<td>Cost per resolution<\/td>\n<td>Unit economics<\/td>\n<td>Trend, not fixed target<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Notice that deflection is #7, not #1. It is useful for capacity planning, useless as a quality measure.<\/p>\n<h2 id=\"metric-1-csat-on-ai-handled-conversations\"><span class=\"ez-toc-section\" id=\"Metric_1_CSAT_on_AI-handled_conversations\"><\/span><strong>Metric 1: CSAT on AI-handled conversations<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This is the metric most teams skip and most regret skipping. How to measure it: after the AI marks a conversation resolved, send a one-click satisfaction prompt (\u201cWas this helpful? \ud83d\udc4d\ud83d\udc4e\u201d or a 1\u20135 scale). Keep it to one question, response rates collapse beyond that. What to do with the results:<\/p>\n<table>\n<colgroup>\n<col style=\"width: 33%;\" \/>\n<col style=\"width: 33%;\" \/>\n<col style=\"width: 33%;\" \/> <\/colgroup>\n<thead>\n<tr class=\"header\">\n<th>CSAT on AI conversations<\/th>\n<th>What it means<\/th>\n<th>Action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>4.5+<\/td>\n<td>Working well<\/td>\n<td>Expand automation scope<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>3.5\u20134.2<\/td>\n<td>Acceptable, tuneable<\/td>\n<td>Review low-scoring transcripts weekly<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>Below 3.5<\/td>\n<td>Hurting more than helping<\/td>\n<td>Narrow the agent\u2019s scope until quality improves<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A high deflection rate with low CSAT is one of the worst combinations because you&#8217;re automating frustration at scale. If CSAT is low, review how the agent responds to complaints and whether it can <a href=\"https:\/\/botsify.com\/blog\/ai-customer-service-escalation\/\">handle angry customers with AI<\/a> without making the situation worse.<\/p>\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-csat-survey.jpg\" alt=\"one-click CSAT survey with thumbs up and thumbs down following an automated support conversation\" width=\"1536\" height=\"1024\" \/><\/figure>\n<h2 id=\"metric-2-first-contact-resolution\"><span class=\"ez-toc-section\" id=\"Metric_2_First_contact_resolution\"><\/span><strong>Metric 2: First contact resolution<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Did the AI actually solve the problem, or did the customer have to ask again? Measure it by tracking repeat contact: if the same customer contacts you about the same issue within 7 days, the first answer did not work.<\/p>\n<table>\n<thead>\n<tr class=\"header\">\n<th>Repeat contact rate<\/th>\n<th>What it means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>Under 10%<\/td>\n<td>Answers are solving real problems<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>10\u201320%<\/td>\n<td>Some answers are incomplete or unclear<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>Above 20%<\/td>\n<td>The AI is deflecting, not resolving<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This metric catches the failure mode that deflection hides: an AI that answers quickly but does not actually fix anything produces lots of \u201cresolved\u201d conversations and lots of repeat contacts.<\/p>\n<h2 id=\"metric-3-escalation-rate-calibrated-not-minimized\"><span class=\"ez-toc-section\" id=\"Metric_3_Escalation_rate_calibrated_not_minimized\"><\/span><strong>Metric 3: Escalation rate, calibrated, not minimized<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Escalation is not failure. It is routing. The right escalation rate depends on your use case:<\/p>\n<table>\n<thead>\n<tr class=\"header\">\n<th>Business type<\/th>\n<th>Healthy escalation rate<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>Simple product, FAQ-heavy support<\/td>\n<td>10\u201320%<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>B2B SaaS with account-specific questions<\/td>\n<td>20\u201335%<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>High-stakes services (finance, health)<\/td>\n<td>30\u201350%<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>Pure FAQ agent on docs site<\/td>\n<td>Under 10%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The goal isn&#8217;t to minimize escalations at any cost. It&#8217;s to make sure the right conversations reach the right people. Effective <a href=\"https:\/\/botsify.com\/blog\/ai-support-ticket-triage\/\">support ticket triage<\/a> helps distinguish routine requests from issues that need human judgment, so the agent doesn&#8217;t attempt to resolve problems beyond its capabilities.<\/p>\n<h2 id=\"metric-4-coverage-by-category\"><span class=\"ez-toc-section\" id=\"Metric_4_Coverage_by_category\"><\/span><strong>Metric 4: Coverage by category<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Knowing that 60% of conversations were handled is less useful than knowing <em>which<\/em> 60%:<\/p>\n<table>\n<thead>\n<tr class=\"header\">\n<th>Category<\/th>\n<th>Volume<\/th>\n<th>AI resolution rate<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>Order status<\/td>\n<td>120\/mo<\/td>\n<td>95%<\/td>\n<td>Fully automated<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>Password reset<\/td>\n<td>40\/mo<\/td>\n<td>90%<\/td>\n<td>Fully automated<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>Refund requests<\/td>\n<td>30\/mo<\/td>\n<td>20%<\/td>\n<td>Agent collects, human decides<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>Bug reports<\/td>\n<td>15\/mo<\/td>\n<td>10%<\/td>\n<td>Triage only<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>Billing disputes<\/td>\n<td>15\/mo<\/td>\n<td>0%<\/td>\n<td>Human from the start<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This view tells you where to invest next. If order status is nearly fully automated, the next win is probably returns or address changes, not more order-status tuning.<\/p>\n<h2 id=\"metric-5-time-to-resolution-ai-vs-human\"><span class=\"ez-toc-section\" id=\"Metric_5_Time_to_resolution_AI_vs_human\"><\/span><strong>Metric 5: Time to resolution (AI vs human)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Compare how long AI-handled conversations take to reach resolution versus human-handled ones:<\/p>\n<ul>\n<li><strong>AI-resolved:<\/strong> usually under 5 minutes end-to-end.<\/li>\n<li><strong>Human-resolved:<\/strong> varies by complexity, but often hours.<\/li>\n<\/ul>\n<p>The value isn&#8217;t simply that AI responds faster. A <a href=\"https:\/\/botsify.com\/website-chatbot\">website chatbot<\/a> can answer routine customer questions outside business hours, reducing unnecessary waiting and giving customers access to support when human agents aren&#8217;t available.<\/p>\n<h2 id=\"metric-6-cost-per-resolution\"><span class=\"ez-toc-section\" id=\"Metric_6_Cost_per_resolution\"><\/span><strong>Metric 6: Cost per resolution<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>AI support can reduce the cost of handling repetitive questions, but only when the agent actually resolves customer issues.<\/p>\n<p>A low cost per conversation means little if customers have to contact support again.<\/p>\n<p>Calculate cost per resolution using:<\/p>\n<p><strong>AI cost per resolution = Total monthly AI support costs \u00f7 Verified AI-resolved conversations<\/strong><\/p>\n<p>Include platform fees, usage charges, maintenance time, and other directly attributable operating costs.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Example_calculation\"><\/span><strong>Example calculation<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Suppose a business handles 2,000 customer conversations each month, and the AI agent successfully resolves 1,000 of them.<\/p>\n<p>Its monthly costs are:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Expense<\/th>\n<th>Monthly cost<\/th>\n<\/tr>\n<tr>\n<td>AI platform and usage<\/td>\n<td>$300<\/td>\n<\/tr>\n<tr>\n<td>Maintenance: 5 hours at $60\/hour<\/td>\n<td>$300<\/td>\n<\/tr>\n<tr>\n<td>Total<\/td>\n<td>$600<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The AI cost per verified resolution would be:<\/p>\n<p><strong>$600 \u00f7 1,000 = $0.60<\/strong><\/p>\n<p>If comparable human-handled tickets cost $6 each, the difference is $5.40 per resolution.<\/p>\n<p>Across 1,000 conversations, that represents $5,400 in potential equivalent handling-cost savings.<\/p>\n<p>However, this is an illustrative comparison, not guaranteed cash savings. Actual savings depend on staffing, ticket complexity, repeat contacts, and whether the reduced workload translates into avoided costs or additional support capacity.<\/p>\n<p>Use your own operating data rather than relying on generic vendor estimates.<\/p>\n<h2 id=\"metric-7-transcript-quality-trend\"><span class=\"ez-toc-section\" id=\"Metric_7_Transcript_quality_trend\"><\/span><strong>Metric 7: Transcript quality trend<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A weekly sample review answers questions dashboards cannot:<\/p>\n<ul>\n<li>Is tone consistent?<\/li>\n<li>Are answers still accurate after product changes?<\/li>\n<li>Are there new question types the knowledge base does not cover?<\/li>\n<li>Are escalations happening for the right reasons?<\/li>\n<\/ul>\n<h2 id=\"metric-8-knowledge-base-freshness\"><span class=\"ez-toc-section\" id=\"Metric_8_Knowledge_base_freshness\"><\/span><strong>Metric 8: Knowledge base freshness<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This is a leading indicator for everything else:<\/p>\n<table>\n<colgroup>\n<col style=\"width: 50%;\" \/>\n<col style=\"width: 50%;\" \/> <\/colgroup>\n<thead>\n<tr class=\"header\">\n<th>Signal<\/th>\n<th>What it means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"odd\">\n<td>High fallback rate<\/td>\n<td>Documents are missing for real questions<\/td>\n<\/tr>\n<tr class=\"even\">\n<td>Repeated corrections to the same answer<\/td>\n<td>Source document is outdated<\/td>\n<\/tr>\n<tr class=\"odd\">\n<td>Escalations on policy questions<\/td>\n<td>Knowledge base has gaps on edge cases<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Set a monthly knowledge-base review as a recurring task. An <a href=\"https:\/\/botsify.com\/blog\/build-ai-faq-agent-cites-knowledge-base\/\">AI FAQ agent<\/a> that answers questions from approved documents depends on accurate, up-to-date source material, so outdated policies and missing information should be addressed before they affect customer responses.<\/p>\n<h2 id=\"building-the-dashboard\"><span class=\"ez-toc-section\" id=\"How_to_Build_an_AI_Customer_Support_Metrics_Dashboard\"><\/span><strong>How to Build an AI Customer Support Metrics Dashboard<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>You don&#8217;t need an expensive analytics platform to track AI customer support metrics. A shared spreadsheet or basic reporting dashboard is enough to get started, provided it captures both customer experience and operational results.<\/p>\n<p>Start with these essential metrics:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Metric<\/th>\n<th>What to measure<\/th>\n<th>Data source<\/th>\n<\/tr>\n<tr>\n<td>AI-handled conversations<\/td>\n<td>Total conversations managed by the AI agent<\/td>\n<td>AI platform analytics<\/td>\n<\/tr>\n<tr>\n<td>AI customer satisfaction (CSAT)<\/td>\n<td>Customer feedback after AI interactions<\/td>\n<td>Post-chat survey<\/td>\n<\/tr>\n<tr>\n<td>Escalation rate<\/td>\n<td>Percentage of conversations transferred to humans<\/td>\n<td>Help desk or AI platform<\/td>\n<\/tr>\n<tr>\n<td>Repeat contact rate<\/td>\n<td>Customers returning with the same unresolved issue<\/td>\n<td>CRM or help desk<\/td>\n<\/tr>\n<tr>\n<td>Resolution rate<\/td>\n<td>Issues confirmed as resolved by AI<\/td>\n<td>Conversation outcomes<\/td>\n<\/tr>\n<tr>\n<td>Cost per resolution<\/td>\n<td>Total AI support cost divided by verified resolutions<\/td>\n<td>Platform billing and internal costs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Start_with_three_priorities\"><\/span><strong>Start with three priorities<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If your team cannot track everything immediately, begin with CSAT, escalation rate, and repeat contact rate.<\/p>\n<p>Together, these reveal whether customers are satisfied, whether the agent knows when to involve humans, and whether problems stay resolved.<\/p>\n<p>Add resolution time, cost per resolution, and category-level reporting as your measurement process improves.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Keep_the_setup_simple\"><\/span><strong>Keep the setup simple<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>You only need a few basic tools:<\/p>\n<ul>\n<li><strong>Conversation logs:<\/strong> Export chat histories from your AI support platform.<\/li>\n<li><strong>CSAT collection:<\/strong> Use a short post-conversation survey.<\/li>\n<li><strong>Escalation tracking:<\/strong> Record human handoffs in your help desk.<\/li>\n<li><strong>Reporting:<\/strong> Use a shared spreadsheet or dashboard to review weekly trends.<\/li>\n<li><strong>Issue tracking:<\/strong> Record recurring questions, failed responses, and knowledge-base gaps.<\/li>\n<\/ul>\n<p>The dashboard should help your team identify problems and decide what to improve. Proper <a href=\"https:\/\/botsify.com\/blog\/ai-agent-integration\/\">AI agent integration<\/a> with your help desk or CRM can bring conversation outcomes, repeat contacts, and escalation data into the same reporting process instead of relying on conversation counts alone.<\/p>\n<section class=\"bt-blog-inline-subs-wrap\">\n<div class=\"bt-blog-inline-subs-inr inline-subs-v3\">\n<h3><span class=\"ez-toc-section\" id=\"Track_What_Matters_in_AI_Support\"><\/span>Track What Matters in AI Support<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Build AI support with better visibility into performance.<\/p>\n<div class=\"inline-subs-cta\"><a class=\"bt-glb-btn\" href=\"\/book-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book a Demo<\/a><\/div>\n<\/div>\n<\/section>\n<h2 id=\"what-good-looks-like-at-30-60-90-days\"><span class=\"ez-toc-section\" id=\"How_to_Set_Realistic_AI_Customer_Support_Metrics_Targets\"><\/span><strong>How to Set Realistic AI Customer Support Metrics Targets<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There is no universal CSAT, deflection, or escalation target that works for every AI support team.<\/p>\n<p>A business answering simple order-status questions will have different results from a SaaS company handling technical complaints or a financial service dealing with sensitive requests.<\/p>\n<p>The most useful starting point is your own support performance before AI implementation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Record_your_baseline\"><\/span><strong>Record your baseline<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Before launch, document:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Metric<\/th>\n<th>Before AI<\/th>\n<th>After 60 days<\/th>\n<th>Change<\/th>\n<\/tr>\n<tr>\n<td>Customer satisfaction<\/td>\n<td>Your baseline<\/td>\n<td>Actual result<\/td>\n<td>Difference<\/td>\n<\/tr>\n<tr>\n<td>First response time<\/td>\n<td>Your baseline<\/td>\n<td>Actual result<\/td>\n<td>Difference<\/td>\n<\/tr>\n<tr>\n<td>Resolution time<\/td>\n<td>Your baseline<\/td>\n<td>Actual result<\/td>\n<td>Difference<\/td>\n<\/tr>\n<tr>\n<td>Repeat contact rate<\/td>\n<td>Your baseline<\/td>\n<td>Actual result<\/td>\n<td>Difference<\/td>\n<\/tr>\n<tr>\n<td>Support hours spent on repetitive requests<\/td>\n<td>Your baseline<\/td>\n<td>Actual result<\/td>\n<td>Difference<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Compare similar question categories wherever possible. An AI agent handling simple FAQs should not automatically be compared with human representatives handling complex disputes.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Review_progress_at_30_60_and_90_days\"><\/span><strong>Review progress at 30, 60, and 90 days<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>First 30 days:<\/strong> Establish baseline performance, identify common knowledge gaps, and use <a href=\"https:\/\/botsify.com\/blog\/a-simple-guide-on-how-to-test-ai-agents\/\">AI agent testing<\/a> to check whether escalation rules and customer responses work as expected.<\/p>\n<p><strong>By 60 days:<\/strong> Review whether customer satisfaction and verified resolution rates are improving. Adjust the agent&#8217;s scope based on recurring issues.<\/p>\n<p><strong>By 90 days:<\/strong> Evaluate longer-term trends in resolution quality, repeat contacts, costs, and human workload.<\/p>\n<p>The objective isn&#8217;t to hit an arbitrary deflection percentage. It&#8217;s to demonstrate that automation improves efficiency without reducing customer satisfaction.<\/p>\n<p>Set targets based on actual support volume, customer expectations, issue complexity, and available human coverage. Revisit those targets as your agent improves.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Common_Mistakes_When_Tracking_AI_Customer_Support_Metrics\"><\/span>Common Mistakes When Tracking AI Customer Support Metrics<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>AI support dashboards can look impressive while hiding serious customer experience problems.<\/p>\n<p>The most common mistake is treating automation volume as proof of success.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Metrics_that_can_be_misleading\"><\/span><strong>Metrics that can be misleading<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<table>\n<tbody>\n<tr>\n<th>Metric<\/th>\n<th>What it might hide<\/th>\n<\/tr>\n<tr>\n<td>High ticket deflection<\/td>\n<td>Customers leaving without getting an answer<\/td>\n<\/tr>\n<tr>\n<td>Thousands of conversations handled<\/td>\n<td>Repeated contacts caused by unresolved problems<\/td>\n<\/tr>\n<tr>\n<td>Very fast response times<\/td>\n<td>Quick but inaccurate answers<\/td>\n<\/tr>\n<tr>\n<td>High automation rate<\/td>\n<td>Customers struggling to reach human support<\/td>\n<\/tr>\n<tr>\n<td>Low escalation rate<\/td>\n<td>The AI handling issues beyond its approved scope<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These numbers are useful, but they need context.<\/p>\n<p>For example, pair deflection rate with CSAT and repeat contact rate. Pair automation rate with escalation quality. Compare response speed with actual resolution time.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Other_mistakes_to_avoid\"><\/span><strong>Other mistakes to avoid<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Measuring only the first month:<\/strong> Early results may fluctuate as the agent is adjusted.<\/li>\n<li><strong>Comparing different support categories:<\/strong> AI and human CSAT should be compared across similar issue types.<\/li>\n<li><strong>Treating every closed conversation as resolved:<\/strong> Verify whether the customer actually received a useful answer.<\/li>\n<li><strong>Ignoring transcript reviews:<\/strong> Numbers reveal patterns, but conversations explain why those patterns occur.<\/li>\n<li><strong>Tracking too many metrics:<\/strong> Focus on measures your team can review and act on consistently.<\/li>\n<\/ul>\n<p>A useful dashboard should make it easier to find problems, not simply make the automation project look successful.<\/p>\n<h2 id=\"setting-up-the-weekly-review\"><span class=\"ez-toc-section\" id=\"How_to_Review_AI_Customer_Support_Metrics_Regularly\"><\/span><strong>How to Review AI Customer Support Metrics Regularly<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Collecting support metrics is only useful when someone reviews the results and acts on them. A short weekly review helps identify inaccurate answers, recurring complaints, and escalation problems before they affect more customers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Weekly_review_30_minutes\"><\/span><strong>Weekly review: 30 minutes<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<table>\n<tbody>\n<tr>\n<th>Activity<\/th>\n<th>Time<\/th>\n<th>What to do<\/th>\n<\/tr>\n<tr>\n<td>Review key metrics<\/td>\n<td>5 minutes<\/td>\n<td>Check CSAT, escalation rate, repeat contacts, and resolution trends<\/td>\n<\/tr>\n<tr>\n<td>Examine conversations<\/td>\n<td>15 minutes<\/td>\n<td>Review five transcripts, including successful and unsuccessful interactions<\/td>\n<\/tr>\n<tr>\n<td>Identify recurring issues<\/td>\n<td>5 minutes<\/td>\n<td>Look for knowledge-base gaps, incorrect answers, and routing problems<\/td>\n<\/tr>\n<tr>\n<td>Assign an improvement<\/td>\n<td>5 minutes<\/td>\n<td>Choose one fix and assign responsibility<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Include both high-scoring and low-scoring conversations in your transcript sample. A customer who gives positive feedback can reveal what the agent does well, while a negative interaction may show where its instructions or knowledge need improvement.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Monthly_performance_review\"><\/span><strong>Monthly performance review<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Once a month, compare performance against your previous results.<\/p>\n<p>Look for changes in customer satisfaction, escalation patterns, unresolved issues, and support costs.<\/p>\n<p>Pay particular attention to situations where automation increases but customer satisfaction declines. That usually deserves a closer look at conversation quality.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Quarterly_review\"><\/span><strong>Quarterly review<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Every quarter, conduct a broader evaluation of the support agent.<\/p>\n<p>Review a larger sample of conversations, audit outdated knowledge-base content, and assess whether the agent should handle additional question categories.<\/p>\n<p>You may also discover that certain issues should return to human support because they require more judgment than automation can reliably provide. Clear <a href=\"https:\/\/botsify.com\/blog\/ai-agent-governance\/\">AI agent governance<\/a> policies help define those boundaries as the agent&#8217;s responsibilities change.<\/p>\n<p>The purpose of regular reviews is to improve customer support, not simply produce another report. Every review should end with a clear action, an owner, and a follow-up date.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-support-metrics-dashboard.jpg\" alt=\"support metrics dashboard showing conversation volume, CSAT trend, and escalation rate over 90 days\" \/><\/figure>\n<h2 id=\"what-to-report-to-leadership\"><span class=\"ez-toc-section\" id=\"How_to_Report_AI_Customer_Support_Performance_to_Leadership\"><\/span><strong>How to Report AI Customer Support Performance to Leadership<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Support leaders need to understand whether AI is improving customer experience, reducing repetitive work, and helping the team manage demand.<\/p>\n<p>A useful monthly report should connect operational metrics with business outcomes.<\/p>\n<p>Include these five elements:<\/p>\n<table>\n<tbody>\n<tr>\n<th>What to report<\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<tr>\n<td>Verified AI resolutions<\/td>\n<td>Shows how much support work the agent completes<\/td>\n<\/tr>\n<tr>\n<td>AI customer satisfaction<\/td>\n<td>Indicates whether customers are happy with the experience<\/td>\n<\/tr>\n<tr>\n<td>Escalation performance<\/td>\n<td>Shows whether complex issues reach the right people<\/td>\n<\/tr>\n<tr>\n<td>Support capacity or cost impact<\/td>\n<td>Connects automation to operational efficiency<\/td>\n<\/tr>\n<tr>\n<td>Improvements made<\/td>\n<td>Demonstrates how the system is becoming more reliable<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Explain_what_the_numbers_mean\"><\/span><strong>Explain what the numbers mean<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Instead of reporting:<\/p>\n<p>&#8220;Our AI agent handled 1,000 conversations.&#8221;<\/p>\n<p>Explain the outcome:<\/p>\n<p>&#8220;Our AI agent resolved 1,000 routine support conversations this month. Customer satisfaction remained stable, and the team used the additional capacity to handle more complex requests.&#8221;<\/p>\n<p>Only report time savings or financial savings when your data supports the calculation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Address_common_leadership_questions\"><\/span><strong>Address common leadership questions<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Why isn&#8217;t deflection higher?<\/strong><\/p>\n<p>Because some issues require human judgment. A higher deflection rate isn&#8217;t useful if customers receive incorrect answers.<\/p>\n<p><strong>Why do AI and human CSAT scores differ?<\/strong><\/p>\n<p>They may handle different types of requests. Compare similar categories before drawing conclusions.<\/p>\n<p><strong>Why do we still review transcripts?<\/strong><\/p>\n<p>Transcript reviews identify issues that summary metrics cannot explain, including outdated answers and inappropriate escalations.<\/p>\n<p>Leadership reporting should demonstrate business value while making limitations visible. Accurate reporting builds more confidence than inflated automation claims.<\/p>\n<section class=\"bt-blog-inline-subs-wrap\">\n<div class=\"bt-blog-inline-subs-inr inline-subs-v3\">\n<h3><span class=\"ez-toc-section\" id=\"Make_Your_AI_Support_Work_Better\"><\/span>Make Your AI Support Work Better<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Get help building an AI agent that resolves customer issues.<\/p>\n<div class=\"inline-subs-cta\"><a class=\"bt-glb-btn\" href=\"\/book-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book a Demo<\/a><\/div>\n<\/div>\n<\/section>\n<h2 id=\"what-to-do-when-metrics-go-wrong\"><span class=\"ez-toc-section\" id=\"What_to_do_when_metrics_go_wrong\"><\/span><strong>What to do when metrics go wrong<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Three common patterns and their fixes:<\/p>\n<p><strong>Pattern 1: Deflection up, CSAT down.<\/strong> The agent is closing conversations without solving them. Fix: read the lowest CSAT transcripts, narrow scope, add escalation triggers.<\/p>\n<p><strong>Pattern 2: Escalation rate climbing.<\/strong> The knowledge base may be outdated, customers may be asking new types of questions, or the agent&#8217;s routing rules may need adjustment. Review escalated transcripts, identify recurring themes, and update the knowledge base. Teams that need help configuring and improving these workflows can use <a href=\"https:\/\/botsify.com\/done-for-you-ai-agents\/\">done-for-you AI agents<\/a> instead of managing every adjustment internally.<\/p>\n<p><strong>Pattern 3: CSAT fine, support team unhappy.<\/strong> The agent is working but the team feels sidelined. Fix: involve them in transcript review and give them ownership of the knowledge base. People support what they help build. Every failing agent I have seen fails in one of those three ways. The fix is always visible in the data, the discipline of looking is the hard part.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-monthly-support-report.jpg\" alt=\"monthly support report showing volume, CSAT, escalation rate, and hours saved\" \/><\/figure>\n<p>&nbsp;<\/p>\n<h2 id=\"faq\"><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions_About_AI_Customer_Support_Metrics\"><\/span><strong>Frequently Asked Questions About AI Customer Support Metrics<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"What_are_the_most_important_AI_customer_support_metrics\"><\/span>What are the most important AI customer support metrics?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Customer satisfaction, verified resolution rate, escalation rate, repeat contact rate, and cost per resolution are useful starting points. Track deflection alongside quality metrics rather than treating it as the main measure of success.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_you_measure_CSAT_on_AI_conversations\"><\/span>How do you measure CSAT on AI conversations?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use a short survey immediately after the conversation. A simple rating or helpfulness question can capture feedback without requiring customers to complete a lengthy form.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Should_AI_and_human_support_share_the_same_CSAT_score\"><\/span>Should AI and human support share the same CSAT score?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Track them separately and compare similar issue categories. Combining the scores can hide differences in performance and customer expectations.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_is_a_good_AI_ticket_deflection_rate\"><\/span>What is a good AI ticket deflection rate?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>There is no universal ideal rate. The right target depends on the complexity of customer questions, the agent&#8217;s approved scope, and whether customers are actually getting their problems resolved.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_often_should_AI_support_metrics_be_reviewed\"><\/span>How often should AI support metrics be reviewed?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Review key metrics weekly during the early stages of deployment. Use monthly reviews for performance trends and quarterly reviews for larger decisions about automation scope.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_should_you_do_when_AI_CSAT_is_low\"><\/span>What should you do when AI CSAT is low?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Review poorly rated conversations, check answer accuracy, identify missing knowledge-base content, and confirm that difficult questions are being escalated appropriately.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_long_does_it_take_to_establish_reliable_performance_metrics\"><\/span>How long does it take to establish reliable performance metrics?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>It depends on conversation volume and consistency. Avoid making major decisions from a small sample of early interactions. Use enough data to identify meaningful trends before expanding automation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Should_customer_support_teams_have_access_to_AI_performance_metrics\"><\/span>Should customer support teams have access to AI performance metrics?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Yes. Support representatives can identify recurring issues, explain customer complaints, and help improve escalation rules and knowledge-base content.<\/p>\n<h2 id=\"final-thought\"><span class=\"ez-toc-section\" id=\"Final_thought\"><\/span><strong>Final thought<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Ticket deflection tells you how much work an AI agent handles, but it doesn&#8217;t tell you whether customers are getting the help they need. That&#8217;s why AI customer support metrics should measure satisfaction, verified resolutions, repeat contacts, escalation quality, and operational costs alongside automation volume.<\/p>\n<p>You don&#8217;t need to track everything from day one. Start with the metrics that reveal customer experience, review conversations regularly, and improve the knowledge base when answers fall short.<\/p>\n<p>The goal isn&#8217;t to make your AI agent look busy. It&#8217;s to build a support system that resolves more issues without compromising customer trust.<\/p>\n<section class=\"bt-blog-inline-subs-wrap\">\n<div class=\"bt-blog-inline-subs-inr inline-subs-v3\">\n<h3><span class=\"ez-toc-section\" id=\"AI_Agentic_Platform_For_Building_Portable_AI_Agents\"><\/span>AI Agentic Platform For Building Portable AI Agents<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Say Hello To Agentic AI That Connects With Your CRM And Even Other Agents<\/p>\n<div class=\"inline-subs-cta\"><a class=\"bt-glb-btn\" href=\"\/book-demo\" target=\"_blank\" rel=\"noopener noreferrer\">Book Now!<\/a><\/div>\n<\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>The support metrics that actually matter for AI agents \u2014 CSAT, escalation calibration, repeat-contact rate, and how to build a review process that keeps quality honest.<\/p>\n","protected":false},"author":1,"featured_media":13527,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify<\/title>\n<meta name=\"description\" content=\"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify\" \/>\n<meta property=\"og:description\" content=\"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\" \/>\n<meta property=\"og:site_name\" content=\"Botsify\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/botsifyapp\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-17T14:43:55+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-17T14:45:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Usama Noman\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Usama Noman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\"},\"author\":{\"name\":\"Usama Noman\",\"@id\":\"https:\/\/botsify.com\/blog\/#\/schema\/person\/6b2e9c8a3a4e8e4e43722952cad555a9\"},\"headline\":\"AI Customer Support Metrics: What to Track Beyond Ticket Deflection\",\"datePublished\":\"2026-10-17T14:43:55+00:00\",\"dateModified\":\"2026-10-17T14:45:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\"},\"wordCount\":3005,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/botsify.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg\",\"articleSection\":[\"Customer Service\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\",\"url\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\",\"name\":\"AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify\",\"isPartOf\":{\"@id\":\"https:\/\/botsify.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg\",\"datePublished\":\"2026-10-17T14:43:55+00:00\",\"dateModified\":\"2026-10-17T14:45:12+00:00\",\"description\":\"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.\",\"breadcrumb\":{\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage\",\"url\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg\",\"contentUrl\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg\",\"width\":1672,\"height\":941,\"caption\":\"AI customer support metrics\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"blog\",\"item\":\"https:\/\/botsify.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AI Customer Support Metrics: What to Track Beyond Ticket Deflection\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/botsify.com\/blog\/#website\",\"url\":\"https:\/\/botsify.com\/blog\/\",\"name\":\"Botsify\",\"description\":\"Botsify Blog | AI Agents, Automation &amp; Business Growth\",\"publisher\":{\"@id\":\"https:\/\/botsify.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/botsify.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/botsify.com\/blog\/#organization\",\"name\":\"Botsify\",\"url\":\"https:\/\/botsify.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/botsify.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2025\/09\/Botsify-Logo-180x60-1.png\",\"contentUrl\":\"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2025\/09\/Botsify-Logo-180x60-1.png\",\"width\":563,\"height\":188,\"caption\":\"Botsify\"},\"image\":{\"@id\":\"https:\/\/botsify.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/botsifyapp\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/botsify.com\/blog\/#\/schema\/person\/6b2e9c8a3a4e8e4e43722952cad555a9\",\"name\":\"Usama Noman\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/botsify.com\/blog\/#\/schema\/person\/image\/b3bcdca1a7af79b6a60a0988bc43a9cc\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9cb3d0d77bb0be4e77a6c8033691feb2?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9cb3d0d77bb0be4e77a6c8033691feb2?s=96&d=mm&r=g\",\"caption\":\"Usama Noman\"},\"url\":\"https:\/\/botsify.com\/blog\/author\/rootadmin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify","description":"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/","og_locale":"en_US","og_type":"article","og_title":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify","og_description":"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.","og_url":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/","og_site_name":"Botsify","article_publisher":"https:\/\/www.facebook.com\/botsifyapp","article_published_time":"2026-10-17T14:43:55+00:00","article_modified_time":"2026-10-17T14:45:12+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg","type":"image\/jpeg"}],"author":"Usama Noman","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Usama Noman","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#article","isPartOf":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/"},"author":{"name":"Usama Noman","@id":"https:\/\/botsify.com\/blog\/#\/schema\/person\/6b2e9c8a3a4e8e4e43722952cad555a9"},"headline":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection","datePublished":"2026-10-17T14:43:55+00:00","dateModified":"2026-10-17T14:45:12+00:00","mainEntityOfPage":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/"},"wordCount":3005,"commentCount":0,"publisher":{"@id":"https:\/\/botsify.com\/blog\/#organization"},"image":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage"},"thumbnailUrl":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg","articleSection":["Customer Service"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/","url":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/","name":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection - Botsify","isPartOf":{"@id":"https:\/\/botsify.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage"},"image":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage"},"thumbnailUrl":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg","datePublished":"2026-10-17T14:43:55+00:00","dateModified":"2026-10-17T14:45:12+00:00","description":"Track AI customer support metrics beyond ticket deflection, including CSAT, resolution rates, escalations, costs, and support quality.","breadcrumb":{"@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#primaryimage","url":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg","contentUrl":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2026\/10\/13118-blog-thumbnail.jpg","width":1672,"height":941,"caption":"AI customer support metrics"},{"@type":"BreadcrumbList","@id":"https:\/\/botsify.com\/blog\/ai-customer-support-metrics-beyond-deflection\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"blog","item":"https:\/\/botsify.com\/blog\/"},{"@type":"ListItem","position":2,"name":"AI Customer Support Metrics: What to Track Beyond Ticket Deflection"}]},{"@type":"WebSite","@id":"https:\/\/botsify.com\/blog\/#website","url":"https:\/\/botsify.com\/blog\/","name":"Botsify","description":"Botsify Blog | AI Agents, Automation &amp; Business Growth","publisher":{"@id":"https:\/\/botsify.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/botsify.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/botsify.com\/blog\/#organization","name":"Botsify","url":"https:\/\/botsify.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/botsify.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2025\/09\/Botsify-Logo-180x60-1.png","contentUrl":"https:\/\/botsify.com\/blog\/wp-content\/uploads\/2025\/09\/Botsify-Logo-180x60-1.png","width":563,"height":188,"caption":"Botsify"},"image":{"@id":"https:\/\/botsify.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/botsifyapp"]},{"@type":"Person","@id":"https:\/\/botsify.com\/blog\/#\/schema\/person\/6b2e9c8a3a4e8e4e43722952cad555a9","name":"Usama Noman","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/botsify.com\/blog\/#\/schema\/person\/image\/b3bcdca1a7af79b6a60a0988bc43a9cc","url":"https:\/\/secure.gravatar.com\/avatar\/9cb3d0d77bb0be4e77a6c8033691feb2?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9cb3d0d77bb0be4e77a6c8033691feb2?s=96&d=mm&r=g","caption":"Usama Noman"},"url":"https:\/\/botsify.com\/blog\/author\/rootadmin\/"}]}},"authors":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/posts\/13118"}],"collection":[{"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/comments?post=13118"}],"version-history":[{"count":9,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/posts\/13118\/revisions"}],"predecessor-version":[{"id":14321,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/posts\/13118\/revisions\/14321"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/media\/13527"}],"wp:attachment":[{"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/media?parent=13118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/categories?post=13118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/botsify.com\/blog\/wp-json\/wp\/v2\/tags?post=13118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}