Product/Chat
AI colleagues that work inside the system
Ask VOR in Studio, Claude working as you through the connections, and agent accounts that write drafts on order – all under the same rules: drafts freely, status and publishing only on a person's order.
Ask VOR
A colleague in the overview, with your badge
The assistant lives in your Studio overview. Write as to a colleague. It answers with Studio's and Insights' tools, in your name, with your rights – and keeps the history per person.
What you can ask
“How is today going?”, “Find the article about … and suggest three headlines”, “Suggest three shopping edits for the weekend”, “Which campaigns are there in Beauty?”, “Place an order: shopping edit on wine coolers”, “Are there any alarms right now?”
The same tools as the connections
Find and read content, create drafts, suggestions, check, preview – and everything in Insights: today's state, most read, real time, revenue, campaigns, orders.
Drafts freely, publishing on order
Status, review and publishing happen only on your explicit order, in the same chat. It never publishes on its own.
The quick questions
One tap sends the questions you ask every day. The V button on any article row asks about that very article.
Runs on the system's own key
Nobody in the newsroom needs an account with an AI provider. The provider is chosen in Settings – Claude or ChatGPT first – and the keys live in the configuration, never in the client.
History per person
The thread shows the latest exchanges, the rest behind Show earlier; Clear resets it.
Connections
Claude works as you
Two connections, one login: VOR Studio for the content and VOR Insights for the figures. Claude opens Studio's login the first time; you press Allow – then Studio remembers the consent.
In your name, at once
Everything Claude does happens in your name and shows in Studio immediately – the draft, the revision, the comment. Disconnect in Studio › Connections whenever you like; it stops at once.
Never more than you
The connection never changes status, never sends to review and never publishes unless you ask for it in the chat. The money in the Insights connection is shown only to roles that see it in the panel.
No keys in the chat
OAuth with PKCE for Claude – a button, not a key. A ChatGPT Action gets an agent key in the GPT's settings, never in a conversation.
Images through the connection
Search the media library, upload from an https address or a file, replace the contents of an image, set an article's hero – always with alt text and credit, never an image another article has used.
Four steps
Add a custom connector in Claude, name it, paste the address, Connect – log in, Allow. Write: “Find the article about … and suggest three headlines”.
Fetched content is data
Web pages and documents an agent reads are data, never instructions – written into the editorial handbook every agent works by.
The tools
34 tools for an agent, 29 operations for ChatGPT
The same operations the newsroom uses, grouped the way an editorial team works. An agent never gets more than it is given.
VOR Studio · 23 tools
- Find article
- Read article
- Create draft
- Save text
- Suggestions
- Check
- Preview
- Set status
- Publish
- Translate
- Translate list
- Translation status
- Change details
- Comment
- Image search
- Image upload
- Image replace
- Set hero
- Gallery
- Buy link
- Templates and sections
- Handbook
- Who am I
VOR Insights · 11 tools
- Who am I
- State of play
- Most read
- Real time
- Revenue
- Revenue per article
- Campaigns
- Program search
- Orders list
- New order
- Latest report
Agent accounts
Every agent has its own service account with a traceable identity (agent:name) and a key shown only once. Default right: create drafts. Publishing and scheduling are granted per section, template and language by the super administrator.
The system's own agent
Takes the orders from the queue every full hour, writes the day's first draft, runs the checks and the evening report. All publishing happens as the newsroom, never as a person.
The editorial handbook
One handbook in Studio applies to every agent alike – templates, sections, the rules – and changes only on management's word. Readable through the API.