Product and implementation guide
Choose a customer journey
ArcApps CRM brings Sales, Marketing, Field Service and Customer Service into a requirements discussion. Confirm the modules included in your setup. Start with one journey, such as an enquiry becoming an opportunity and then a service handoff. Define what each stage means and which person owns the next action. A status label should reflect an observable business condition.
Example: an accepted proposal
A salesperson records proposal acceptance, but operations still needs authorization to schedule work. Keep commercial progress distinct from readiness for delivery. Identify the agreed scope, contacts, service location and approval evidence required at the handoff. Test an incomplete handoff and confirm that the receiving team can identify what is missing.
Records, duplicates and permissions
Agree whether customer means an organization, an individual or both in your process. Use stable identifiers where supported and define how duplicates are reviewed. Do not merge unrelated people solely because their names match. Restrict notes, documents and exports according to the approved audience, and avoid placing sensitive information into broadly visible free-text fields.
Follow-up and connected work
Notifications and tasks need a responsible owner, an understandable status and a route for unavailable staff. Confirm any marketing, field or support integration explicitly; shared branding does not imply automatic data exchange. Use the CRM handoff guide to prepare ordinary and exception cases for a tailored demonstration.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support