{"id":5160,"date":"2026-06-23T01:43:17","date_gmt":"2026-06-23T01:43:17","guid":{"rendered":"https:\/\/basecode.com.au\/stagingforcallation\/?post_type=case-study&#038;p=5160"},"modified":"2026-06-23T06:50:11","modified_gmt":"2026-06-23T06:50:11","slug":"national-funeral-services-provider","status":"publish","type":"case-study","link":"https:\/\/basecode.com.au\/stagingforcallation\/blog\/case-study\/national-funeral-services-provider\/","title":{"rendered":"National Funeral Services Provider"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">For the largest funeral services operator in Australia and New Zealand, the phone is where almost every customer relationship starts. Families call in their most difficult moments. Every one of those calls matters.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Across several hundred locations and dozens of brands, the volume of calls that network generates every day is enormous. That volume is a business asset &#8211;\u00a0 if you know how to use it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This provider did not just want a reporting dashboard. They had their own internal data lake and business intelligence tools already in place. What they needed was structured call data &#8211; raw, detailed, and engineered to plug directly into their own analytics pipeline.<\/span><\/p>\n<h2><b>The Problem<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Standard reporting was not enough.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The provider needed call data that could flow cleanly into their own systems &#8211; structured to match their data lake, ready to query without manual processing, and reliable enough to sit alongside sales figures and customer spend data in their own BI tools.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Without that, the call data their network generated every day was going to waste.<\/span><\/p>\n<h2><b>What Changed<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Custom call data fed directly into their data lake meant Callation built reporting output engineered specifically to fit the provider&#8217;s own data structure. The data arrived clean, structured, and ready to query &#8211; no manual reformatting, no intermediate steps.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Correlation against sales and spend data meant analysts could match call volumes against sales figures and average customer spend inside their own BI tools. Callation provided the call side of that picture &#8211;\u00a0 precise, granular, and reliable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Missed call identification across the network meant every unanswered call across every location was logged and visible. Analysts could identify missed calls at any level &#8211;\u00a0 individual funeral home, region, or network &#8211; and the teams responsible could follow up directly.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Security roles meant data flowed to the right person at the right level. Location managers saw their location. Regional managers saw their region. National analysts saw the full network. No one saw more than they needed to.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Five years of call data retained by default gave analysts the depth of history needed to run meaningful trend analysis across hundreds of locations. The data was there, clean and accessible, whenever it was needed.<\/span><\/p>\n<h2><b>The Outcome<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Call data now feeds directly into the provider&#8217;s BI and analytics pipeline. Call volumes are matched against sales data and customer spend. Missed calls are identified, followed up, and opportunities are recovered before they are lost.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Almost every arrangement begins with a phone call &#8211; often from someone in distress, often time-sensitive. At this scale, a missed call is not just a lost booking. It becomes a measurable pattern. With the right reporting in place, that pattern is visible and the network can act on it.<\/span><\/p>\n<h2><b>About Callation<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Callation is a cloud-based platform for call reporting, accounting, and analytics. It works across a wide range of phone system vendors and platforms. Reports are built for accuracy and simplicity, the platform is cloud hosted with no servers to manage, and data is retained for five years as standard with options to extend.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>For the largest funeral services operator in Australia and New Zealand, the phone is where almost every customer relationship starts. Families call in their most difficult moments. Every one of those calls matters. Across several hundred locations and dozens of brands, the volume of calls that network generates every day is enormous. That volume is [&hellip;]<\/p>\n","protected":false},"featured_media":5226,"template":"","meta":{"_acf_changed":false},"categories":[31],"tags":[],"case-study":[],"class_list":["post-5160","case-study","type-case-study","status-publish","has-post-thumbnail","hentry","category-case-studies"],"acf":[],"_links":{"self":[{"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/case-study\/5160"}],"collection":[{"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/case-study"}],"about":[{"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/types\/case-study"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/media\/5226"}],"wp:attachment":[{"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/media?parent=5160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/categories?post=5160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/tags?post=5160"},{"taxonomy":"case-study","embeddable":true,"href":"https:\/\/basecode.com.au\/stagingforcallation\/wp-json\/wp\/v2\/case-study?post=5160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}