How Time Zone Email Router works
Press Load model once: your browser downloads Gemma 4 E2B instruction-tuned (web build) (2.0 GB) from this site and keeps it in its cache. Then add your text and press Classify locally. The model runs on this device using your graphics card, so nothing you enter is sent to a server. Until the model is loaded, or if your device cannot run it, the tool falls back to a simple keyword check and labels the result as the fallback.
Gemma 4 E2B instruction-tuned (web build) is a small open language model from Google. The tool sends it the instruction below plus your text, asks for a JSON answer with fixed fields, and shows each field as a card. It runs at temperature 0, so the same input gives the same answer on the same device, though different graphics cards can word it slightly differently.
Inputs longer than 6,000 characters are cut to that length before they reach the model, and the result says so. The model only sees what you paste: it does not look anything up.
The instruction the model gets
You read a scheduling email that involves people in different places. Extract the proposed times, the time zones or cities attached to them, and who is where, all exactly as written. Do not convert any time to another zone and do not work out dates; another tool does the conversion.
What it returns
- Proposed times: Each proposed meeting time with its zone or city exactly as written, e.g. '4pm London time, next Monday'.
- People and locations: Each person or party and the place or zone the email puts them in, written as 'Name: place'.
- Zones to check: Every distinct time zone or city in the email, once each, so you can convert the proposed time for each.
- Unclear details: Times without a zone, ambiguous abbreviations such as 'EST in summer', or relative dates like 'next Monday'.