ShiftSynch training

Updated October 17, 2026. This guide prepares you to qualify a scheduling customer, demonstrate the setup-to-review workflow, and explain paid publishing and referral rewards accurately.

Who the current product is built for

ShiftSynch’s current main offering focuses on home-care and nursing teams that need roles, rotations, staffing requirements, and help identifying potential call-in staff. Good prospects include coordinators in home health, assisted living, skilled nursing, and clinical staffing who repeatedly rebuild schedules or struggle to see coverage gaps.

The central workflow is semi-automated: define the rules, generate a schedule where the plan permits it, and have a responsible person review the result. Sara, the assistant, can help with supported setup and coverage questions. A generated grid or assistant response is not a guarantee that every local labor rule, credential, availability change, or patient-care need has been satisfied.

Historical pages may discuss other industries such as fire departments. If a prospect has a specialized requirement, demonstrate that requirement directly before recommending a subscription. Do not promise a complete payroll service, clinical records system, automatic legal compliance, emergency dispatch, or an integration merely because scheduling data exists.

Discover the scheduling problem

Ask the coordinator:

• How many teams and staff need to be represented?
• What are the shift names and start/end times, including overnight shifts?
• Which roles or qualifications are required for each shift?
• Do staff follow repeating rotation tracks, and how long is each cycle?
• How are time-off and availability handled now?
• Who approves the final schedule and sends changes to staff?
• What happens when someone calls out?
• Is the immediate need to build a draft or publish a working schedule?

Distinguish staff count from the number of people working on a particular day. Ask how staffing requirements vary by team and day. A prospect who says “ten nurses” may mean ten employees, ten per shift, or ten full-time-equivalent positions; those are different inputs.

Summarize one outcome: “You want a reviewed night-shift schedule and a short list of eligible people to contact when there is a gap.” That gives your demo a purpose.

Plans, annual billing, and trial routes

The current pricing page lists:

Free is a valid draft-building starting point, but publishing/notifying staff, automatic generation, exports, and Sara coverage answers require a paid plan. Qualification-gated assignment is advertised on Professional, not Free or Basic. Do not call Basic a credential-enforcement plan simply because a qualification concept appears elsewhere in the application.

Annual advertised “per month” figures are monthly equivalents of an annual bill: Basic $7.50 equivalent is $90 paid annually; Professional $39 equivalent is $468 annually; Enterprise $79 equivalent is $948 annually. Read the checkout total before purchase.

The pricing page advertises a 14-day no-card paid trial. The current paid registration path, however, says Continue to Checkout, states that payment details are entered next, and says no card is charged until the trial ends. Explain the route the customer actually sees. Free signup is clearly offered without a card; do not promise that every paid trial route avoids collecting one. Have the customer review trial eligibility, renewal date, charge amount, and cancellation terms before committing.

Lesson 1 — Start the account and choose the team

Have a new customer begin from your own current ShiftSynch link in the Residual Apps dashboard. Use Start Free — No Card Required to explore the Free path or the relevant paid offer if the customer has chosen it. The customer enters their own work email and completes the account process; never collect their password or card.

After signing in as the responsible administrator, use the Admin Dashboard. Its team selector determines which team’s setup and schedule you are working on. Check it before every major change. A multi-team account can otherwise produce a perfectly valid schedule for the wrong team.

The dashboard’s Initial Setup area links to team, qualification, FTE, crew, shift, staffing-requirement, rotation, and staff management, followed by schedule views and publishing. The scheduling-manager and staff-facing views have different purposes. A customer who lacks an administrative control may be signed in with an employee role.

Do not create real employee accounts in a demo. Use an authorized demo organization and synthetic identities, without an email address belonging to another person.

Lesson 2 — Define shifts before building rotations

In the shift-management screen, define each shift with its Shift Code, optional name, start time, end time, and sort order. A code is one to five characters. Use Create Shift and verify the saved row.

For a demonstration, use codes such as D and N with fictional times. In the real organization, use the coordinator’s actual times and confirm how an overnight shift spans dates. If a schedule looks wrong by a day, examine times and date context before manually moving many assignments.

The staffing and rotation screens depend on defined shifts; they explicitly direct the administrator to create shifts first when none exist. A sensible order is team → shifts → relevant qualifications/FTE/crews → staff → requirements/rotations → schedule review. Do not fill a rotation with undefined codes and assume they will become shifts automatically.

Professional customers can configure the required qualifications for their actual workflow. A qualification entry must reflect real verified staff information. Adding a label does not independently check a professional license or certify a worker.

Lesson 3 — Add staff and assign the correct context

Open staff management and choose + Add Staff Member. The current form includes email, name, role, team, crew, FTE code, qualifications where available, and status. It also offers password handling; use the organization’s approved onboarding process and never ask staff to reuse an owner’s credentials.

Review role carefully. Access roles control what someone can do in the application; a clinical qualification describes what work they are qualified to fill. They are not interchangeable. Assign the intended team and crew so coverage questions refer to the right group.

The staff screen provides search and team/crew/role/status filters. If someone seems missing, clear the relevant filter and inspect their status before creating a duplicate. Confirm staff capacity under the chosen plan before onboarding a large roster.

Where assigning a rotation track to a person, select the intended Rotation Track and Start Date. An incorrect start date shifts the pattern even if the pattern itself is correct. Review a sample week after saving.

Lesson 4 — Build rotations and staffing requirements

In rotation management, select the team and enter a Track Name, Number of Weeks in Cycle, and optional description. The pattern grid has Sunday through Saturday columns and one row per cycle week. Fill the pattern using the actual defined shifts. Fill Example is a teaching aid; it is not a recommended staffing pattern for a real agency. Clear Pattern is a deliberate change.

In Staffing Requirements, choose the team or intentionally apply a requirement across teams. Select the Shift, an optional qualification, start/end dates, and Rotation Weeks. An empty team selection can apply broadly, so verify scope before saving.

The requirement grid uses click to increase a count and Shift+Click to decrease it. Enter the number of required staff for each day/week of that repeating pattern. A blank end date can mean an ongoing requirement. Review the saved requirement rather than assuming a filled example reflects the organization’s needs.

A rotation says how work repeats; a staffing requirement says how much coverage is needed. A schedule can follow rotations and still have a coverage gap. That is why generation must be followed by review.

Lesson 5 — Use Sara and review the schedule

Sara can help apply supported nursing setup and answer paid coverage questions. Give specific context: the team, date, shift, required roles, and the question. For example, in a synthetic demo: “Who is on Tuesday night, and who could be called in without a rest conflict?” Use dates explicitly when ambiguity matters.

Treat the answer as a starting point for the coordinator’s review. Check the named staff against current availability, approved time-off, qualification data, rest constraints, and actual operational requirements. A stale staff record can produce an unsuitable suggestion even if the assistant correctly reads that record.

Where the paid schedule-generation controls are available, generate only after the inputs are correct. Review the target team, month/date range, each critical shift, and gaps or conflicts. Do not generate repeatedly to hide a configuration problem. If a result is unexpected, work backward through staff track start dates, shift definitions, requirements, and availability.

Before publishing, confirm that the person responsible for staffing has reviewed the final grid. The software supports that work; it does not take responsibility for clinical staffing decisions.

Lesson 6 — Publish intentionally

The schedule view shows a publishing area with Publish & notify staff. The current action publishes a selected team’s schedule for a month and emails staff their shifts. The confirmation names the month/year and warns that staff will be emailed. This is a real communication action, not a harmless preview.

Check team, month, staff email data, assignments, and approval before confirming. In training, show the control without sending anything to real staff. A Free account can encounter a paid-feature gate; that is expected.

After publishing, review the status and notified count. The code distinguishes published shifts from successful emails, including cases where notification enablement causes messages to be skipped. “Published” does not prove every staff member received, opened, or acknowledged an email.

Republishing after changes can resend notifications. Coordinate that action with the scheduler instead of clicking repeatedly because an inbox is slow. For a missing notification, verify the recipient/account, notification setting, published period, and spam folder, then escalate with the visible result.

Paid export controls provide schedule outputs such as grid, PDF, or Excel options where available. Verify the selected team/date range and actually open the downloaded file. A saved spreadsheet is not automatically synchronized after later schedule edits.

Lesson 7 — Time-off, billing, and support

Availability and time-off requests belong in the relevant workflow so the schedule reflects the organization’s decisions. A submitted request and an approved absence are different states. The coordinator should inspect status and the affected dates before generating or revising assignments.

The administrator dashboard has a subscription/billing management link. Use the customer’s existing account to review subscription, invoices, and billing. Read the portal before confirming changes. Canceling a subscription and deleting organization information are different actions; neither should be used as a quick fix for a missing schedule.

For a payment/activation issue, keep the purchase reference, account email, and plan information. Do not create another organization or pay again before support checks the original transaction. For access issues, confirm role, team, plan and trial status first.

Product support is support@shiftsynch.com, as listed on the pricing page. Include organization/account email, team name, affected date range, screen, exact error, browser/device, and whether publication or email occurred. Remove staff personal information that is not needed. Never email passwords, full card data, or sensitive patient details.

A practical eight-minute demonstration

Prepare a synthetic team with fictional staff and no real recipient inboxes. Use a paid demo only when paid access is actually available.

1. Ask team size, shift pattern, and the biggest coverage problem.
2. Show the selected team and a Day/Night shift definition.
3. Show one staff member’s team, role, and rotation start date.
4. Open one repeating rotation and one matching staffing requirement.
5. Review a sample schedule and point to a coverage question Sara can answer on a paid plan.
6. Explain the human review before publication and show Publish & notify staff without sending.
7. Match the customer’s team/staff count and qualification needs to a plan.
8. Offer one next task: configure the first team and two real shift definitions in their own account.

A Free demo can show draft setup while explaining which next steps require payment. Do not pretend a paid feature has run when the account is gated.

Sales language and common objections

Introduction: “How do you rebuild coverage when a nurse calls out? ShiftSynch organizes shifts, rotation patterns, and staffing requirements, with paid coverage assistance and publishing. I can show you a small draft schedule. I’m an affiliate and may earn a commission if you purchase through my link.”

“Our spreadsheet works.” Ask whether reviewing coverage or communicating updates is the hard part. If the current process meets their needs, do not invent a savings claim.

“Does Free email the schedule?” No. Publishing/notifying, generation, exports, and Sara coverage require a paid plan.

“Can Basic enforce credentials?” The current qualification-gating offer is Professional. Choose by requirement as well as staff count.

“Will it automatically comply with every rule?” No. Keep configuration accurate and retain responsible human review.

“The trial page asks for a card.” Different entry paths currently use different wording. Read the actual checkout; do not guarantee a no-card paid trial.

“Published means everyone received it?” No. Check the notification result; receipt/opening is separate.

An invited follow-up can be: “Did the first rotation land on the correct dates, and have you checked the requirements for the hardest shift?” These examples do not initiate an outreach cadence.

Referral credit and earnings

Copy your personal ShiftSynch share link or QR from Residual Apps. New customers should open it before registering, preferably in the same browser. A staff invitation, schedule export, or generic login URL is not your affiliate link. Existing accounts, browser storage, device changes, and checkout handoffs can affect attribution.

The current published reward is 40% of qualifying paid plans: Basic $3.60/month or $36/year; Professional $19.60/month or $187.20/year; Enterprise $39.60/month or $379.20/year. Annual rewards correspond to qualifying annual payments, not monthly payouts based on an annual headline price.

A Free registration, a trial, or a link click is not a paid sale. Standard Residual Apps terms keep 20% of commissions earned, capped at $9.99/month; refunds, cancellations, qualification, and program terms can affect earnings. These are gross reward examples, not guaranteed take-home income. See the partner-program training for payout mechanics. Referral support is support@residualapps.com.

Readiness quiz and answers

1. Eight staff, one team, draft building only? Free can fit.
2. Same team needs publishing and generation? Basic is the first advertised paid fit.
3. Thirty staff or credential-gated assignments? Review Professional.
4. Rotation versus requirement? A repeating work pattern versus needed coverage.
5. A track starts on the wrong date? Fix/review its start date and resulting schedule, rather than accepting a shifted pattern.
6. Can you publish during a demo to show it works? Only in an authorized synthetic environment with no unsuspecting recipients; otherwise show the control.
7. Basic annual gross reward? $36 for a qualifying annual payment under current terms.
8. Sara’s answer removes human review? No.

Practice selecting the team, defining a shift, reading a rotation and requirement, locating the publish boundary, explaining annual totals, and copying the correct disclosed referral link.

Use the app and help us improve it

Use the app yourself before recommending it. Complete one useful workflow in your own account or an authorized demo, then find the saved result again. A paid subscription is not required to become a partner; use the free option or an available preview and be clear about what you have actually tried.

If you use this app, tell us what works, where you get stuck, bugs you can reproduce, and what you wish it did next in Partner Care. Include the app, web/iOS/Android, installed version or browser version, steps, expected result, and what happened. Say whether it affects your own use or a demonstration. Please report unclear training or a screen that differs from this guide too.

Keep customer names, email addresses, medical records, payment details, passwords, and sign-in codes out of feedback. Use fictional examples and remove private information from screenshots. Urgent account or billing problems still belong with the product support route above.