Internal requests: one assistant for the whole team
The team asks internal questions and requests its tasks from an assistant that knows the company. Whatever needs a decision reaches the person who decides.
The problem
“Everyone asks me.” Where a document is, how to request something, how a customer's request is going. Internal questions always interrupt the same people, the ones who know the most and have the least time.
It happens in any company with departments and processes that repeat. Each request arrives through a different channel, and the answer has to be looked up and written by hand.
How it is done today
Whoever has a question writes to the person they think knows, through whichever channel is closest. That person drops what they were doing, finds the answer and replies. The same question comes back the following week, from someone else.
What was asked for in conversation is recorded nowhere, and nobody knows where it stands.
How we solve it
- The team writes to it in the channel they already use, in their own words: a question, a task or how something is going.
- If it is a question, it looks for the answer in what it knows about the company and replies saying where it comes from.
- If it is a task an agent already handles, it starts it and leaves the result prepared for whoever has to approve it.
- If it needs a decision, it takes it to the person who decides, with what they need to decide.
- It logs every request, and when someone asks how it is going, it answers with its status.
Result
100 %of internal requests go through the assistant
In our own company, all internal requests go through the assistant, which has been in production since September 2026.
What it takes
Timeline
It starts with the questions that come up most and grows process by process. How long it takes depends on how well organised your company's knowledge is. The exact timeline comes out of the assessment.
Data and access
Your internal documentation: how each thing is done and where it is. Who can see what. And read access to the tools where the status of requests is checked.
Your tools
Your team's messaging channel, your ticketing tool and your document repository. The team does not learn a new tool.
How it is built
Knowledge is kept separate per customer and per project, with no mixing: one customer's information does not show up in an answer about another.
Actions that change something outside, such as sending, publishing or paying, need a person's approval. What the assistant does on its own is read, prepare and log.
No password goes through the conversation: credentials are kept in a secrets manager and handed only to the process that uses them.
What it reads in an email, a document or a website is treated as data, never as instructions.
Frequently asked questions
Where do people ask the assistant?
In the messaging channel your team already uses. There is nothing new to install or learn.
Can the assistant see all the company's information?
It sees what you decide. Knowledge is kept separate per customer and per project, and each person looks up what they are entitled to.
Does it carry out tasks on its own?
It prepares and logs. What goes out to a customer, is signed or moves money is always approved by a person.
Does it also handle customer requests?
Yes. It logs them, looks up the information and prepares the reply, which a person approves. That is covered on the support page.
What does Julditec do?
We implement the agent, adapt it to your company, train your team and maintain it. The day-to-day work is done by the agent; deciding and approving stays with your team.
Related automations
Support
Every support email turned into a ticket with its label, its owner and the reply prepared.
Voice assistant
The phone, always answered: the assistant takes notes on the call and alerts the right person.
Part of Customer service and support