# Native feature or custom connection? Decision worksheet

Fireflax · Version 1.0 · Reviewed 8 October 2026

Companion to https://fireflaxgpt.com/resources/native-crm-or-custom-automation

Open this file in a text editor and keep your completed copy locally. No account, integration, data upload or automatic message is created by this worksheet. Use fictional records while testing. Do not put credentials here.

## Your bounded workflow

- Task and start condition:
- Responsible person:
- Intended next action / completion condition:
- Current software, exact plan, region and role:
- Native feature to inspect:
- Official documentation and date checked:
- Hands-on observation, settings, test date and tester (or “not tested”):
- Data needed and where each fact is recorded:
- Permission owner and supported way to access that data:
- Reply, opt-out, changed status and missing-information checks:
- Failed connection / duplicate / retry behavior to test:
- Pause procedure and effect on already pending actions:
- Maintenance owner and next review date:

## Compare the approaches

For each option record the gap it solves, the evidence you have, and what is unknown.

1. Keep the current manual process or configure an existing reminder:
2. Add a simple native rule with explicit conditions:
3. Connect systems through a verified supported interface:
4. Add AI assistance to a reviewed draft, only if needed:
5. Defer until ownership, data or risk is understood:

Costs: separate an existing subscription from an upgrade, connector usage, AI usage if any, setup work and ongoing support. Record currency, period, workload assumptions and current provider terms. No product price is assumed by this worksheet.

Chosen option and why:

Smallest fictional test that could disprove the choice:

## Fictional filled example

- Business: Cedar Example Plumbing; quote Q-104 for a tap replacement.
- Task: review a quote sent on 5 October 2026 on 8 October 2026. Three calendar days is an illustrative choice, not a recommended cadence.
- Owner: Alex, office coordinator. Outcome: one recorded next action after checking the latest conversation.
- Native option to investigate: an internal quote reminder in the existing software. Jobber's Work Settings documentation describes one; account access and actual behavior were not tested.
- Data: quote state, last conversation, telephone notes and contact preferences. Whether they are available together is unknown.
- Exceptions: a request for a revised quote goes to Alex; a stop request prevents follow-up; an unclear current state is held for review.
- Initial decision: investigate the internal reminder. No AI or custom connection is justified until a specific gap is demonstrated.
- Maintenance: Alex is the fictional owner. No real Fireflax staffing or service commitment is created.
- Next test: confirm who sees the reminder, check a changed quote, and record a telephone reply before any customer contact.

## Provider questions

- Is this available in our exact plan, region and role?
- Is the result an internal task, a draft, or an automatic send?
- Which replies/status/preferences stop it, including replies elsewhere?
- What happens to pending actions after a rule is edited or disabled?
- How do we inspect a failure or duplicate before retrying?
- What are the incremental costs and who maintains the setup?

## Sources and limits

Documentation checked 8 October 2026; no Jobber login, integration test, customer evidence or performance result is claimed.

- https://help.getjobber.com/en/articles/work-settings/
- https://help.getjobber.com/en/articles/automations/
- https://help.getjobber.com/en/articles/custom-automation-builder/
- https://www.getjobber.com/pricing/

This is a planning worksheet, not authorization to contact someone or a claim of product compatibility. Confirm appropriate contact and timing for the real relationship and channel.