PILOT SCOPE OUTLINE
For discussion · one dealership
DEALERSHIP PARTS FOLLOW-UP
A weekly report.
A clear next call.
Give your parts team assigned customer lists, a current specials flyer, and a routine for recording what happens next. Start with one compatible report and one dealership.
Agreed report setup, rep mapping, team walkthrough and the first three weekly reviews.
Your dealership uploads the report. Includes rep packages, outcome tracking and automatic rep delivery after the initial reviews.
Quoted after
the report check
An alternative monthly plan for an agreed scheduled report email. Same reviewed-to-automatic delivery process.
Pilot pricing. Scheduled intake is not included in the $99 Upload plan. Report compatibility, exact scope, support and commercial terms are confirmed in writing before commitment.
What Loom Labs delivers
A working dealership setupValidate the agreed report, configure the workspace, map source rep IDs and check actual recipient addresses.
A complete rep call packageLatest invoice per customer, duplicates removed within the report, phone issues flagged, assigned lists, conversation starters and your selected PDF flyer.
A review and delivery routineRep email packages, printable lists and CSV exports, plus a manager summary. Review the first three distinct weekly runs together.
Visible follow-throughReps record call outcomes and next steps. Managers see activity and separately labeled, rep-reported new orders.
How the pilot starts
- Check report fit
Inspect a sample through an agreed private handoff, confirm the roster and intake method, then finalize the written scope and invoice.
- Set up and review
Configure the dealership and flyer, train the team, and activate reviewed sending after report and recipient checks.
- Enable automatic delivery
After three reviewed weekly sends, your workspace owner can enable automatic delivery.
Publishing or downloading a list does not send it. Reviewed sends need approval; automatic mode needs separate owner activation and fresh, validated reports.
What your dealership provides
A named owner and team
A manager to approve weekly runs, the correct rep IDs and emails, manager copy recipients, and a dealership reply-to address.
The agreed report and flyer
A fresh weekly report with its week and as-of date, plus the current monthly PDF with an expiry date. Use a flyer under 2 MB for email, or explicitly choose no flyer.
People making the calls
Reps work the assignments and save outcomes. Your team corrects source data in the DMS and verifies any newly reported orders.
Time for the first three reviews
Check lists, recipients and package content in three distinct weeks. Agree support contacts and the review schedule before launch.
Agree what success looks like
Capture the baseline before the first run. Compare the same tasks and a similar reporting period after the reviewed runs; choose targets together before starting.
| Measure | Before the pilot | During and after |
|---|---|---|
| Preparation time | Minutes to export, clean, assign and distribute a list. | Minutes for the same work, including review and corrections. |
| Follow-up completed | How the team currently records worked customers and next steps. | Unique customers worked, useful conversations and follow-ups completed. |
| Verified outcomes | Agree who verifies orders and what evidence counts. | Match reported orders to dealer records; distinguish existing demand from genuinely additional business. |
Historical invoice totals are prior activity. Rep-reported orders are unverified until reconciled. Neither proves incremental sales, and no revenue result is guaranteed.
Scope to confirm before launch
This pilot covers one dealership and an agreed compatible HTML-style report or Reconnect CSV template. It does not include arbitrary Excel/DMS formats, DMS integration, payment processing, customer autodialing or unlimited custom development.
Scheduled email intake must be verified with the actual report sender before unattended use. Missing inputs or an expired flyer stop automatic processing. Provider acceptance is not proof of inbox delivery; uncertain sends pause for investigation.
Final scope and terms—including deliverables, support, start date and payment timing—are agreed before work begins.
Bring the report.
We’ll check the fit.
Request a walkthrough, review the scope together, and agree the first weekly run.
reconnect.loomlabs.dev/demo