← GraftG blog

When GraftG doesn’t understand your message

You do not need special commands — but GraftG does need enough detail to know what you mean. Here is what each type of message needs.

1 August 2026 · 4 min read

GraftG reads normal English, not a command language. When it says it did not understand, the message is nearly always missing one piece of information — or is trying to do two things at once.

Mileage needs a distance and a where

"38 miles to the Hartley job" works. "Went to Hartley" does not — there is no distance. Include the number and a short description and it logs first time.

Quotes need a customer and a price

"Quote for Dave Jones, replace boiler, 2 days labour, £480 parts" has everything: who it is for, what the work is, and the money. Drop the customer name or all the figures and GraftG has to ask.

Receipts should be a clear photo, on their own

Send the photo by itself rather than attached to a paragraph of other instructions. Flat, well-lit, whole receipt in frame — see why a receipt fails to scan.

One thing per message

"45 miles to Smiths and quote them for a rewire" is two jobs in one sentence. Send them as two messages and both land cleanly.

If it still cannot read it

Rephrase rather than repeat — the same wording will fail the same way. And if a specific phrasing keeps failing, it is worth telling us: email hello@graftg.co.uk so we can teach it.

FAQ

Do I need to use special commands with GraftG?

No. You write in ordinary English. There are a few shortcuts like MILES REPORT or QUOTES for summaries, but everyday logging is just a normal sentence with the key details in it.

Why does GraftG keep asking me questions?

Because something it needs is missing — usually the distance on a mileage message or the price on a quote. Answer the question and it completes the entry; include that detail next time and it logs first time.

Try it free for a month

Solo from £14/month — first month free. No app to install.

Get started free