Automation route

The best route to fully automated Mob Deals

The safest architecture separates source monitoring from price publication. Automation should collect evidence, but humans or strict validation should approve any price before it appears as a recommendation.

Chosen architecture

1. Source intelligence

Daily GitHub Action checks 64 public sources and writes data/live-sources.json with reachability, final URL, status and price-like tokens.

2. Normalisation

Provider records stay in data/providers.json; manual deal records stay in data/deals.json. This prevents scraped tokens becoming fake prices.

3. Human approval

A review issue should be opened when source tokens change. Only approved changes update public deal cards.

4. Assisted switching

The switching page already provides PAC/STAC/INFO SMS helpers. A future support line can guide older users step-by-step.

5. Compliance and privacy

Do not collect PAC codes until a real support process, privacy policy, retention policy and secure storage exist.

6. Decision engine

Rank plans by user need: keep number, network, data, budget, roaming, contract length, accessibility and risk labels.

Why this route wins

  • It gives live public signals now without repeating the original fake-scraping issue.
  • It scales to almost every provider/source because unreachable pages become visible review tasks.
  • It protects older/non-technical users by making the official PAC route simple before building paid phone support.
  • It keeps compliance manageable: no PAC storage, no personal data collection, no misleading price guarantees.

Future assisted phone line

A real phone line is possible, but it needs a business number provider, trained script, call-recording decision, privacy update, escalation process and data-retention rules. The best first implementation is a callback/support request that never stores PAC codes unless strictly necessary.

Implementation milestones

  1. Now: provider directory, live source checks, PAC/STAC/INFO helper, public roadmap.
  2. Next: source-change detection that opens GitHub issues for review.
  3. Then: provider-specific deal extractors with tests and human approval.
  4. Later: assisted callback line and optional AI decision helper with source citations.