Fill in a form after a job. The rest of the pipeline takes it from there.
The content intake workflow is the entry point for the entire content pipeline. A Tally form submission triggers BackCrew to capture the brief, normalise the fields, and drop it into the content queue — ready for scheduling without anyone touching a spreadsheet.
Good content comes from real jobs. Getting that detail out of the technician's head is the bottleneck.
The best content a pest control company can post isn't written by a marketing agency — it comes from what actually happened on a job that day. A specific pest. A specific location. Something a customer said.
The problem is capturing that before it's forgotten. The intake form is a simple, fast way for a tech or owner to submit a brief right after a job — location, complaint, what was found, anything worth sharing. Takes under two minutes.
From there, BackCrew handles everything. The brief lands in the queue and the pipeline picks it up automatically.
Tech or owner submits a Tally form after a job — location, complaint, pests found, anything worth sharing
Webhook fires to BackCrew the moment the form is submitted
Fields are normalised and a new row with status = pending is written to the content queue sheet
A control record is logged. If anything fails, an error record is written instead and flagged for review
05.1 Scheduler Sequencer picks up the pending row on its next daily run and assigns a post slot
Tally form webhook — fires on submission, no polling
Google Sheets content queue — one row per brief, status tracked through the pipeline
05.1 Scheduler Sequencer picks up pending rows daily and assigns the post slot