Monitoring service records form part of a safety-critical
emergency response ecosystem. To ensure client information remains accurate,
traceable, and properly synchronised across all relevant systems, all
amendments to existing monitoring services must follow a controlled change
management process.
Individual Modification Requests Required
A separate Modifications request (ticket) must be submitted
for each client service requiring updates.
This process applies regardless of whether one or many
services require changes.
Examples of changes include:
Emergency
contact updates
Contact
phone number changes
Key
safe detail changes
Client
name corrections
Miscellaneous
notes updates
Other
client/service record amendments
Each individual ticket creates a controlled audit trail
showing:
who
requested the change,
what
was changed,
when
the request was submitted,
when
the change was completed,
and
confirmation that the request was actioned.
This process also assists with synchronisation across
multiple integrated systems involved in monitoring, emergency response,
telecommunications provisioning, and compliance recordkeeping.
While submitting separate requests for multiple services may
initially seem onerous, this approach ensures that each amendment can be
independently tracked, verified, and audited historically through to
completion.
Bulk-Edited Spreadsheets Cannot Be Accepted
Exported reconciliation reports are provided as reference
documents only and are not intended to function as editable amendment forms or
source-of-truth records.
However, providers are welcome to re-run reports from the
Member Portal at any time. Each report is generated live from our systems at
the time of export and therefore reflects the most current data available
within Daktel’s platform. This can be useful for periodically reviewing
services or validating that previously submitted modification requests have
been completed correctly.
Daktel Australia cannot accept:
marked-up
spreadsheets,
highlighted
reports,
files
containing comments or notes,
spreadsheets
with added/removed columns,
or
bulk edited reconciliation exports for processing.
These types of documents create ambiguity, weaken audit
traceability, and significantly increase the risk of interpretation,
processing, or data synchronisation errors across integrated systems.
For this reason, all amendments must be submitted
individually via separate Modification tickets.
Why Large Volumes of Changes Occur
Large batches of corrections are commonly caused by:
delayed
periodic reconciliation,
historical
updates not previously submitted,
local
records diverging over time,
or
services being changed internally without corresponding modification
requests being lodged with our Service Desk.
Providers should periodically review and reconcile client
monitoring data to ensure records remain accurate and up to date.
Ticket Subject Naming Convention
When submitting modification requests, please use a
meaningful, unique email subject line to facilitate efficient triage and
tracking.
Recommended format:
[Client Name] – [Service Identifier] – [Request Type]
Example:
Margaret Smith – 0491 574 632 – update emergency contact
phone number
This is especially important where multiple requests are
being submitted simultaneously.
Important
The Daktel Service Desk reserves the right to return or
reject:
This policy exists to protect the safety of your service end-users,
maintain the integrity of emergency response data, and ensure accurate
historical recordkeeping across all systems.
Thank you for your understanding and cooperation in helping
maintain the accuracy, integrity, and reliability of your clients’ monitoring
services.

This article's audience is for registered Support at Home service providers only. For myhomefone retail consumer support,
click here for the main menu.