Skip to content
Agentic Ag

Flag the blocks to test for smoke taint after a smoky week

Smoke during ripening can taint wine and make fruit unsaleable, and wineries may reject fruit without a test result. Testing takes time, so the request has to go in well before the pick.

The Vintage coordinator logs the smoke days, lists the blocks at the most sensitive stage and drafts a request to the winery about smoke taint testing before picking.

When · Daily
Bushfire smoke over the vineyard for more than a day between veraison (when grapes start to colour) and harvest
You get
Smoke days logged by block and stage; blocks at most risk; testing request drafted to the winery
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
Orchards and vines

What it reads

  • Smoke observations and fire warnings
  • Block growth stages
  • Winery requirements for smoke testing in the contract

What you get

  • Smoke days logged by block with growth stage
  • The blocks most at risk
  • A draft request to the winery about testing

When it stops and asks you

  • Smoke was patchy and some blocks may have missed it
  • The winery hasn’t said what it needs
  • Picking is due within the testing time

How often

In fire seasons, a few times a decade

Who uses it

OwnersManagers

What it uses

Live

Weather forecast

The team uses the forecast to find spray windows, warn you about heat and frost, and plan for dry spells.

Live

Inbound email

Forward invoices, kill sheets, NVDs, soil tests and emails from your stock agent to your own farm address. The team reads each one, sums it up and suggests who handles it.

Exploring

Fire, flood and heat warnings

If we get access, the team would see the same warnings you do and check your plan against them.

The last one makes it better, but it works without it.

Nothing official leaves the farm without your yes.This job runs at Act with approval: prepares it fully. You tap yes. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Vintage coordinator

Started 5:40am · Daily

Start to done
5 min
Agent actions
2
Needed you
2×
[AGENT NAME]For the Vintage coordinator

Daily check · 5:40am

Smoke from the [fire name] fire over the vineyard for 2 days

Vintage coordinator

Noted the smoke days and checked block stages and the contract

2 days of smoke over the vineyard. 4 blocks are past veraison: Shiraz 4, Cabernet 6, Chardonnay 2 and Pinot 3. The contract lets [winery] ask for smoke testing. Draft a note asking what they want and when?

[AGENT NAME] · 5:40am

Yes. Pinot’s due in 10 days, flag that.

You · 5:42am

Vintage coordinator

Drafted the note with smoke dates and blocks

Note to [winery]: smoke [date] to [date], 4 blocks past veraison, Pinot 3 due in about 10 days, asking what testing they want. Send it and log the smoke days?

[AGENT NAME] · 5:42am

Approved

Send it.

You · 5:45am

Done · 5:45am1 waiting for you

  • Smoke days logged by block with growth stageSaved
  • The blocks most at riskSaved
  • A draft request to the winery about testingWaiting for you

Behind the scenes

  1. 5:40am

    Trigger Daily check

    Smoke from the [fire name] fire over the vineyard for 2 days

    • forecast.readsmoke haze
    • Block stages: 4 of 6 past veraison
  2. 5:40am+7 sec

    Vintage coordinator works on it · 1 step

    Noted the smoke days and checked block stages and the contract

    • documents.readcontract says the winery may ask for testing
  3. 5:40am+2 sec

    [AGENT NAME] messages you

    “2 days of smoke over the vineyard. 4 blocks are past veraison: Shiraz 4, Cabernet 6, Chardonnay 2 and Pinot 3. The contract lets [winery] ask for smoke testing. Draft a note asking what they want and when?”

  4. 5:42am+3 min

    You reply

    “Yes. Pinot’s due in 10 days, flag that.”

  5. 5:42am+7 sec

    Vintage coordinator works on it · 1 step

    Drafted the note with smoke dates and blocks

    • plans.draftnote to [winery]
  6. 5:42am+2 sec

    [AGENT NAME] asks for your yes

    “Note to [winery]: smoke [date] to [date], 4 blocks past veraison, Pinot 3 due in about 10 days, asking what testing they want. Send it and log the smoke days?”

  7. 5:45am+3 min

    You approve

    “Send it.”

  8. 5:45am+3 sec

    Vintage coordinator Done

    Note sent to [winery]; smoke days logged by block; Pinot pick date flagged pending their reply

    • email.send
    • memory.remembersmoke event [date]
    • records.log_readingsmoke [date] to [date]

An example with made-up data. Names and figures in [brackets] are placeholders.

Put [AGENT NAME] to work on your farm.

We’re taking a small number of pilot farms in [REGION]. Start with one or two agents and add more as you go.

Pilot farms wanted

Want to try it out?

Join the pilot, or book a demo and we’ll walk you through this job on a farm like yours. You text the team from your phone. Some connections are still being built, and we’ll tell you which.

  • Weather forecast
  • Inbound email
  • Fire, flood and heat warnings
  • Nothing to install

Free report

Getting started with AI.

A free practical guide for Australian farms and agribusinesses

Where AI actually helps on a farm, what it needs from you, the risks to watch, and a 90-day plan to start small.

  • Where it actually helps
  • What it needs from you
  • Risks and guardrails
  • Working out the return
Book a demoJoin the pilot