Office Agent Showdown: What Makes the New Rising Force TeleAgent Qualified to Get a Seat at the Table?

The office Agent market has entered a fierce competition phase in the second half of the year.

When you open such products, most items on the left sidebar look familiar: files, search, skills, scheduled tasks, PPTs, and web page generation. AI has gradually moved beyond the chat box to enter computers and handle specific work tasks.

However, in daily work, the issues we care most about are often as follows:

Can it read multiple files in different formats? If requirements are modified midway, can it still remember the previous background information? Can the deliverables be opened directly? Are the numbers consistent? How many points will be consumed to run one task?

These specific links are reshaping the competition in the office Agent track. A one-time generation can attract users to try, while long-term use depends on delivery, consumption and functional boundaries.

Recently, APPSO noticed that a product called TeleAgent has joined this wave of office Agent. It is a desktop Agent launched by China Telecom, built on the self-developed Xingchen large model and domestic intelligent computing base.

It sounds a bit unexpected that an operator enters the market to develop a personal office Agent. However, the model, computing power, security and service capabilities accumulated by China Telecom over the years are exactly the standard configurations required by current Agent capabilities, which makes us more curious about TeleAgent.

We are more concerned about what results it will deliver after being put into real work, and how different its experience is from other Agent products. APPSO will show you the actual test results right now.

As a relentless demanding party, can AI still cope with all requirements?

This time, I decided to experience the fun of being a demanding client.

I first asked TeleAgent to make an activity plan, the task was to prepare an activity for the simulated brand "Qike Coffee". The project initiation description, budget unit price, confirmation rules and supplementary materials were all stored in the folder, mixed with past experience documents.

It needed to sort out a large number of existing project documents, then produce a project Excel sheet, a one-page execution instruction and 8 pages of editable PPT, and additionally keep a work log to record every modification made.

The first version it delivered was a brand exchange meeting with 160 guests, and listed the details of division of labor and materials.

With the initial plan ready, I started to modify the requirements repeatedly to let TeleAgent feel the changeable demands of real clients.

First, change the event name to "Qike · After-work Friday Party", reduce the number of guests to 100. And require it not to be designed like a business summit, make the copywriting more relaxing, and keep other contents unchanged.

When TeleAgent updated the work log, it did not directly take "100 guests" as the total number of attendees. The details confirmed in the previous version were also completely retained. For the past materials added midway, it did not arbitrarily take them as new requirements for this activity.

Then, I cut the budget from 120,000 yuan to 80,000 yuan. It chose to remove the souvenir part and reduce the cost of the afternoon tea break at the same time.

That's not all, I pushed the opening time from 14:00 to 16:00, kept the date and duration unchanged. The check-in, rehearsal, staff arrival and material entry all needed to be postponed accordingly.

Then the venue was also modified, it needed to re-plan the scheme according to the new venue size and price. Meanwhile, I asked it to try to use white background and orange color for the PPT.

At this point, ordinary office workers would have already collapsed. TeleAgent said nothing, silently updated the log, and finally delivered a full set of documents according to the latest requirements.

In the final execution plan, it adjusted strictly according to each round of modification. We checked all changes item by item, and they were indeed consistent with the feedback details.

TeleAgent supports a context of more than 400K Tokens, which allows it to remember these frequently changing requirements, and help me complete the delivery like an excellent and diligent office worker.

Master of Scheduling for New Semester

For another task, we switched to students' daily arrangement. The requirements of six courses are scattered in the syllabus, timetable screenshots and course notifications, in addition to club on-duty and internship schedules. Each material is not complicated when viewed alone, but problems will arise when they are put together.

For example, classes and on-duty tasks conflict in the same afternoon. The teacher said in the group chat that the presentation date would be modified, but the syllabus still showed the old one. Without sorting out all the semester tasks, it is difficult to decide what to prepare first this week.

We asked TeleAgent to sort out a semester task sheet, a 16-week plan, and make a "Weekly Task Dashboard" that can be opened in a browser. For unconfirmed dates, we required it to keep different statements.

In the finished Excel sheet, homework, exams and reading requirements are all available. Next to each task there are dates, scoring requirements and sources. When you need to verify a certain assignment, you can go back to the original file according to the source. The unannounced final presentation time was not filled with a guessed date.

Semester task sheet: columns for courses, dates, scores, status and sources.

The presentation of user research course is particularly prone to scheduling errors. The syllabus says it is on October 29, the group notification says it is planned to be changed to the 30th, but the educational administration department has not confirmed it yet.

TeleAgent kept both dates. If arranged on the 29th, it will conflict with the project management course; if changed to the 30th, it will overlap with the internship. It clearly explained these two situations. The confirmed conflicts in the first week were also listed: statistics class overlaps with club on-duty, mandatory tutoring overlaps with part-time work schedule.

Open the "Weekly Task Dashboard", you can directly check what needs to be submitted in the next few days. Interview plans, proposal descriptions and data cleaning assignments all appear under the corresponding dates. Click to the mid-term presentation week, the conflicts caused by the two pending dates mentioned earlier will also be displayed. The web page is saved locally, and can be opened even without internet connection.

There is also a very thoughtful detail: in the 16-week plan, it also made separate arrangements for the autumn break and exam week.

Weekly Task Dashboard: 7-day schedule, conflicts and preparation suggestions in advance.

Recently, the discussion on "whether people without Tokens are not qualified to go to university" has aroused heated debate. In fact, for student groups, they still need to consider what kind of Tokens to bring, after all, AI has become a new cyber stationery.

It is worth mentioning that after the task is completed, it will give skill modification suggestions. You can save this workflow as a reusable skill, and you can also share it publicly with others.

On TeleAgent's skill leaderboard, I also found that the top skill on the soaring list is not for office work at all, but a skill called "Fantasy Hero Biography", which is a turn-based role-playing RPG web game developed by CheLia referring to Ragnarok Online. There are many other interesting skills like this, and you can take a cyber break while waiting for the Agent to finish office tasks.

A 5-person small team preparing for a product launch event

Finally, we arranged a product launch preparation task for TeleAgent.

The simulated team has only 5 people, preparing to recruit the first batch of beta users for "Shixu". The folder contains the founder's scattered notes, 10 user interviews, as well as function lists, cost sheets, Logos and two interface sketches.

There is also old information in these materials. The early notes mentioned recruiting 100 people, but the officially approved quota is 50 people. The price and launch date have also been modified. We required it to sort out these differences first, and then prepare introduction materials and recruitment web pages according to the confirmed requirements.

The first round of delivery includes product positioning, recruitment plan, two-week action schedule, a 6-page PPT and web prototype. The introduction adopts the officially confirmed information. Open the PPT and web page, you can see the Logo and color matching in the materials, and the product name, price and launch date are also consistent.

The requirements it sorted out from the interviews are related to the problems this product aims to solve: first find out the tasks to be done from the materials, see the impact when the date changes, and have a place to view the weekly schedule at ordinary times. Each type of requirement is attached with the interview number. Some users want team collaboration, but this function is not included in the first release, and it is not written as available in the introduction.

The two-week action schedule records who is responsible and when to complete the task. Which functions the development team needs to finish, when to prepare the recruitment copy, and who will screen the applications, all have corresponding arrangements.

The web page can be opened directly locally. When you try to fill in the form, you will be reminded if you miss the name or enter the wrong email; after filling in, the page will display the content you filled in. It also notes that this is a demonstration, and there is no real registration backend.

At this point, we temporarily modified three things: the beta user quota was reduced from 50 to 30, the price was not disclosed for the time being, and the newly confirmed "product data is only stored locally" was added. The launch time and free experience arrangement remain unchanged.