Frequently Asked Questions

No, Act! servers for Australian customers are in the Amazon datacentre in Sydney, Australia.

Yes, Act! has SOC2 certification and is compliant with the Australian Privacy Act 1988.

AI drafts marketing content, and summarises customer information and history, to save you time and close faster.

Yes—automated post-job requests and referral prompts boost social proof and repeat work without manual chasing.

Import contacts, create 3 pipeline stages (New → In Play → Won/Lost), add 3 email templates, and set daily “Next Step” tasks. Small setup, immediate lift.

Done right, it reduces admin by auto-logging emails/calls and nudging next steps; the goal is fewer, smarter actions per sale.

It tags contacts by interest, triggers emails or SMS after actions, and shows what content converts—so you spend time on messages that bring bookings.

Yes. Modern CRMs are cloud-first with mobile apps so you capture notes, calls, and tasks on the go—no admin pile-ups at night.

No—consistent reminders, pipelines, and templates lift reply rates and renewals; even small lists see outsized ROI when you systemise follow-up.

It starts as an address book of everyone you deal with; capturing leads, customers, suppliers, and more; effortlessly collecting all the information about each contact or company; including all the calls, meetings, tasks, messages & opportunities; all at your fingertips every time you interact with someone; and then automating follow up.
You stop losing time in spreadsheets and DMs and start following up consistently—meaning more wins from the same pipeline.

Some contracts prefer AU data centres..Act! servers for Australian customers are in the Amazon datacentre in Sydney, Australia.

Yes—automations can request reviews and track response, lifting visibility in local packs and conversions.

Model total cost: seats + add-ons + implementation + integrations. Simpler tiers reduce hidden costs and speed ROI.

Built-in is simpler for SMBs and ensures better attribution; separate tools can add power but increase cost & maintenance.

Yes—dedupe rules, required fields, select-from-list, validation, and integration reduce junk data and improve reporting and forecasting.

Email/calendar, website forms, accounting/billing, support inbox, and ads—so every touchpoint feeds one customer record.

Keep processes simple, automate logging, and tie dashboards to team goals; many CRM projects struggle without this behavioural focus.

Within days, not months, if you start with core objects (contacts, deals), email sync, and 1–2 automations—then iterate. This phased approach lifts adoption.

Lead response time, task completion, pipeline velocity, renewal/upsell rate—because follow-ups become automated and visible.

It pulls interactions into one profile so teams see history, next actions, and lifecycle value—leading to faster cycles and fewer handoff drops.

Track cycle time, win rate, forecast accuracy, CSAT/retention, and cost-to-serve; these are the leading indicators of payback.

Identity/SSO → email/calendar → data lake/warehouse → support/commerce → ads/marketing—to keep records consistent from day one.

Start where revenue leakage is highest (e.g., response time in sales or churn in service), then expand—measurable wins build momentum.

Executive sponsorship, frontline champions, time-boxed training, and dashboards tied to team incentives.

Prioritise a golden customer record and enforce integration standards so insights and AI aren’t starved.

Documented Privacy Act alignment, SOC2 certification, breach processes, role-based access, encryption at rest/in transit, and regional data options.

Create a value playbook: 2–3 high-impact use cases, clear owners, 90-day outcomes; avoid sprawling pilots that stall.

Summarise all recent interaction, Lead scoring, next-best action, personalised marketing content generation—if your customer data is unified and trusted.

Use regional data stores and clear cross-border controls; Australia has no blanket data-localisation law but requires Privacy Act compliance for offshore transfers.

Adoption—complexity and unclear value stall rollouts; design for frontline usability and phased wins to avoid failure patterns.

No-code/low-code CRMs reduce change lead-time and empower business teams to ship updates without heavy dev queues.

Treat it as a data & workflow platform that unifies channels and feeds AI/analytics; siloed tools erode trust and reporting.

Assess usability, local support, integrations, pricing transparency, and compliance posture; AU guides and roundups help shortlist options.

Standardise fields, automate capture, remove duplicates, and connect every touchpoint so AI works on complete, trusted data.

Messy data, over-complex setups, and weak training; simplify, clean, and coach to avoid common failure patterns.

Unified history enables faster, more personal responses across channels—customers feel known, not bounced between teams.

Solos: operational with simple automation; SMBs: operational + collaborative; enterprises: all three plus analytics for planning and AI.

Operational (automation for sales/marketing/service), Analytical (insights/forecasting), Collaborative/Strategic (share data across teams/partners). Choose based on your bottleneck.