Customer contact tools in Albany can bring enquiries and messages together, but signing a contract commits the business to more than an inbox layout. The arrangement needs to explain the work supplied, information handled, continuing charges and responsibilities when something changes.
This planning guide sets out questions at successive decision points. It concerns selecting a contact tool, not determining the legal effect of a particular clause. Where the agreement is unclear or consequential, obtain suitable legal or specialist assistance.
Before approaching providers: what contact work needs support?
Define the channel and task. Handling product questions, updating existing customers and sending marketing messages are different activities. A tool may support several without making their responsibilities interchangeable.
Record who receives a message, who responds and what counts as resolved. Include a request needing clarification or a handover during an absence so the requirements reflect more than the easiest case.
Keep customer-facing promises tied to actual capacity. A tool that receives messages continuously does not mean staff can provide answers continuously, or that a provider supplies that service on the business’s behalf.
At the requirements gate: what must the proposed service do?
Ask providers to explain how the same defined workflow operates under the quoted plan. Identify essential capabilities, such as assigning responsibility or preserving the context of a customer correction.
Check which channels, users and records are included. A headline contact limit or message allowance needs a definition before it can support a useful comparison.
Separate a confirmed capability from something requiring an additional service, manual workaround or future development. Record unresolved requirements instead of converting broad assurances into verified features.
Before a trial: what information will be used?
Use appropriate fictional messages and authorised participants for an initial exercise. Do not upload a real contact list merely because a provider wants to populate a demonstration quickly.
The OAIC’s privacy practice guidance recommends considering privacy early, limiting collection and examining third-party handling. Ask what information the provider receives, its purpose and who can access it.
Check the obligations applicable to the business rather than assuming every small operator has identical coverage. Also ask what happens to records after a trial ends and what conditions apply to deletion or continued retention.
At the communication gate: how are different permissions recognised?
A person asking a service question has not automatically agreed to receive ongoing promotions. The workflow should preserve the purpose of the contact instead of silently treating every enquiry as a marketing subscription.
ACMA’s spam guidance explains consent, sender identification and unsubscribe requirements for marketing emails and messages. Outsourcing the sending does not remove the business’s responsibility to have the required consent.
Ask how relevant consent evidence and opt-outs are maintained where marketing is in scope. A technical sending feature is not proof that a proposed audience may lawfully receive a campaign.
Before accepting a price: what work and commitment are included?
Obtain the complete charging basis for setup, use, users, support and necessary connections. Identify assumptions behind usage charges and any change in price after an introductory period.
Ask who prepares records, configures routing, trains staff and checks the resulting workflow. A modest subscription may be appropriate while leaving those tasks with the business.
For an Albany team working with a provider elsewhere, confirm delivery format, support availability and the stated time zone. Avoid assuming an online offer includes on-site setup or immediate personal assistance.
At the contract gate: what counts as agreement and change?
The ACCC’s contracts guidance explains that acceptance can occur through words or actions, including online acceptance. Do not treat the absence of a paper signature as proof that no commitment exists.
Review how the agreement describes scope changes, renewal, ending the service and obtaining necessary records. Seek clarification before relying on a cancellation or refund assumption that the actual arrangement does not support.
Keep provider answers with the applicable document versions. A useful comparison should make clear which questions are settled, which depend on a condition and which still require professional help.
Ask whether an exit export preserves message relationships, current responsibility and the context of a customer correction. A list of contact names alone may be insufficient for continuing unresolved work. Use an authorised sample to examine meaning as well as the number of exported records.
Before rollout: what would justify proceeding?
Use a final decision note covering:
- The contact task and channels selected.
- The sample workflow and limitations observed.
- The information handling and relevant permissions.
- The complete cost and retained business work.
- The support, renewal and exit arrangements.
- The unresolved questions and responsible person.
Check what staff must maintain after launch, including access, routing instructions and unresolved messages. A contract can define an arrangement without ensuring that the business has resourced its part.
An Albany business is better prepared to commit when the customer journey and the provider’s responsibilities are both understandable. The decision should follow a workable service arrangement rather than a convenient-looking contact screen.