Synchroteam

Run a representative job from scheduling and technician assignment through field report, parts use, invoice and customer receipt. Repeat with lost connectivity, a reschedule and a multi-job invoice to test the steps most likely to expose permission or synchronization gaps.

Confirm Standard versus Premium routing, mobile-device count, connector data flow, payment-module terms and portal access with the vendor. The official descriptions do not verify a time saving, an accounting reconciliation result or a successful card settlement for a particular business.

The Standard plan excludes Route Optimization, while Premium lists the full feature set. A scheduling calendar and ScheduleAssist should therefore not be treated as proof that one-click route optimization is available in Standard. Confirm the chosen plan and exact optimization workflow.

The mobile app shows work orders, changes and attachments, and can record job-report milestones, signatures, photos, barcodes and parts used. Stock controls include quantities, serialized parts and transfers. Set field permissions and report templates before rollout.

Synchroteam describes an automatic offline mode for the mobile app and an onboard database. Trial the specific jobs, attachments, payments and synchronization sequence that technicians need when signal is weak; the vendor page does not prove every feature works offline in every configuration.

A customer portal can expose job activity, reports and invoice history through a revocable link. A service-request form can be enabled. Check which records and attachments each link reveals, how access is revoked, and whether gallery access carries an extra charge.

For a Synchroteam custom report, set the date, technician, job status, type and customer filters before exporting, then check a sample Excel file. Synchroteam says the export includes all jobs displayed after the report runs and does not honor a later keyword filter. Larger reports may be emailed to an editable recipient, while very large reports require narrower filters. Check the recipient and expected rows before sharing or relying on the file.

During a mobile field trial, include a failed-sync recovery check. Synchroteam advises checking the connection and forcing sync first; reinstalling the app or selecting WIPE ALL DATA deletes unsynchronized reports. Confirm the last successful synchronization date before any wipe, and stop if it has not updated. No device, report or synchronization was tested here.

For recurring service, test whether Synchroteam should only create each job or also schedule it. Its recurrence setup supports frequency, dates and a specific time or scheduling window; the guide distinguishes create-only from create-and-schedule paths. A window is a time preference, not a guaranteed appointment: if unavailable, Synchroteam may place the job elsewhere, and overlapping jobs show a conflict that staff can reschedule. In a harmless trial, inspect generated jobs and the technician calendar over several cycles before promising a customer a fixed visit window.

Before a field team uses PDFs to check mobile billing, map its correction route. Synchroteam says a technician-created invoice or quotation syncs to Back Office for a manager to review and send. An invoice can be deleted in the mobile app only before synchronization, and generating the PDF automatically synchronizes it; afterward, the mobile delete option for invoices and quotations is unavailable. Test the sequence with a harmless draft and confirm how the office corrects a post-sync mistake before issuing live invoices.

Before deleting a Synchroteam technician, review upcoming assignments and keep at least one Administrator in place. Synchroteam says the deleted person's jobs, job reports and activities remain accessible, and their schedule remains visible for past dates. It documents restoring a deleted user from Trash but warns that deleted data stay there for no more than a month. Use a fictional technician to check past records, future jobs, replacement access and the account's restore window before an actual offboarding.

Before using Synchroteam attachments as a field document library, check its 2 MB file limit and accepted PDF, Word, text, Excel and image types. The vendor says attachments can be linked to customers, sites, equipment or jobs and sent to technicians' mobile app. Marking an attachment Private hides it from technicians and clients; administrators and managers retain visibility. Use fictional files on representative records to compare mobile and customer-portal views under intended roles, and plan another path for oversized or sensitive files if that test cannot meet the team's needs.

Synchroteam says a Private job-report item is omitted from the customer PDF. Changing a field's visibility or conditional behavior in a published template can also affect jobs created in the past; minor changes affect only future interactions. The vendor recommends duplicating the template before major edits. In a test account, compare fictional jobs created before and after the change, including their customer-facing PDFs, before editing a live template.

If customers can create jobs through Synchroteam's portal and technicians will claim them from the Job Pool, test the handoff explicitly. The vendor says the option to add new jobs to the pool by default applies to user-created jobs, not portal-created jobs. A portal-created job that is added to the pool needs a team or user scheduling preference for technicians to see it. Follow a fictional portal-created job through office review, pool placement, preference setup and the intended technician's job list before promising self-assignment.

Before treating a signed Synchroteam job report as final, check its Signature control setting. The vendor says that, when this option is activated, changing the report after signing deletes both the technician's and customer's signatures. Its Options guide lists the control under Job Reports. With a fictional job and authorized test signers, make a harmless post-sign correction, verify both signatures clear, and agree how fresh sign-off is obtained before sending the corrected report to a customer.

Do not assume Synchroteam's map automatically records a technician's travel. The vendor says an administrator must enable Time Tracking and create a Travel activity; the technician must manually activate mobile Tracking, start that activity and grant GPS permission. Background data or refresh is needed to keep coordinates flowing while the app is in the background. Before using this with staff, confirm who can see locations, how device permission and staff acknowledgment work, and what travel data is retained. Plan the check with fictional jobs before collecting real travel locations.

Before using Synchroteam notes as customer-facing updates, use vendor demo data to compare a note left unmarked with one marked Public in the customer portal. The official Help article says a Public note is displayed there; it also says Job, Customer and Site timelines track messages sent manually or by automation, with job-report PDFs in the Job timeline and invoices unrelated to a Job in the Customer or Site timeline. Ask the vendor to show where an example message appears and who can see each note. Confirm portal scope, user permissions and notification setup for the quoted plan. Treat a timeline entry as an activity record, not proof that the customer received or read a message. No real note or message was created.

Before importing staff holidays or absences into Synchroteam, preview a fictional CSV with one row assigned to a technician and another with both technician and group fields blank. Its Activities guide says an import needs the activity name and start and end dates, offers Preview for field mapping, and schedules a blank-assignment row for all technicians. An Unavailability activity creates a conflict if a job overlaps. Ask the vendor to show the mapped rows, intended recipients and any overlapping job in a safe demonstration before a real import. Do not assume Preview alone prevents a broad schedule change.

Before enabling Synchroteam Strict Invoicing, compare a fictional invoice created before the switch with one created after it. The vendor says activation is not retroactive: an earlier Created invoice remains editable without an automatic credit note. With the setting active, Drafts can be fully modified or deleted, but changing protected fields on a Created, Sent, Paid or Late invoice cancels it, creates a credit note and opens a new Draft. Have the billing owner review that correction trail and the handling of any payment before using real invoices; the guide does not establish refund behavior or legal compliance.

Before sending a Synchroteam Customer Portal link, use a fictional customer with no live link to choose whether access should cover one Job, a Site or all work for that Customer. The guide says the Back Office provides a secure link to copy and send, and Reset revokes it. An older official release note also describes a private access key for two-step portal access. In a test account, inspect visible customer details, attachments and Jobs, confirm whether an access key is required and who may copy or reset the link, then reset a test link and retry it in a separate browser. Do not treat Reset as retracting information already viewed.