Preview of the upcoming agency workspace. Processes and Marketer AI are already available in your project.
Client portfolios, alerts, results and team activity in one overview. Owners can see where a decision is needed and who is handling it.
No account needed: switch between projects, alerts and your team in the owner overview.
| Project | Alerts | Spend |
|---|---|---|
| North | 2 | 640 € |
| Studio | 1 | 480 € |
| Trail | 0 | 920 € |
Use one review to identify where an owner’s decision is needed. A project requiring a response, a stable campaign and missing data share an overview that guides the team to the appropriate work.
Compare project results over the same period, check connection status and open tasks. Weak performance needs campaign analysis; a missing connection first needs data restored, not an assessment of the specialist.
Open the issue from the portfolio queue, review its importance and owner. The team overview helps account for planned workload when assigning work instead of assuming everyone has spare capacity.
The team can complete a step manually, with a copilot or through AI. Return to task history and response and resolution times. Assess handling alongside the difficulty of the issue and its eventual outcome.
With multiple clients, control cannot stop at campaign status. You need to know what needs a decision, who owns the issue and whether the team can take on another task. A shared portfolio brings these perspectives together.
Start with the project table: performance, open issues and alerts side by side. Choose the client who needs a conversation or a change in priorities, then open the task and its history. See whether the difficulty is in the campaign, data access or work waiting on the team.
Walk into the meeting with decisions to make and people responsible, without collecting status updates from every specialist.
Assign new tasks with workload, deadlines and the nature of the work in mind. Compare the plan with tracked time, response time and resolution time. When an issue changes hands, keep its evidence, decisions and completed steps together instead of starting the handover from scratch.
Know who can take on the work, what is holding up progress and which specific question to take back to the client.
Open your task from the list, kanban board or timeline. Inspect the related campaign in Sembot or go to Google Ads or Analytics. Complete a step manually, prepare it with a copilot or delegate a supported action to AI, keeping the context for the next person.
Start with a specific object and question; the result of your work stays available to the whole team.
These scenarios show how to connect routine checks with team execution. Pick a situation familiar to your agency and explore the relevant example without creating an account.
Choose a project. Open a task. See how your team and AI take the next step in an example, without creating an account.
Compare project statistics and review alerts in a shared queue. Move from a client result to the actual task instead of collecting updates from different tools.
Assign tasks and track time worked, time to first response and time to resolution. Interpret the numbers alongside task type, workload and responsibility.
Share AI across the team instead of arranging a separate subscription for each person. Portfolio management is an add-on to Marketer AI or Professional; project capacity and White Label are separate choices.
Spend, conversion value and ROAS describe performance according to platform data. Open tasks and alerts describe work to handle. Read them together, but do not treat ROAS as profit or an empty source as a zero result.
The plan shows who can take work. Tracked time describes actual work, while response and resolution times describe task handling. A shorter time alone does not prove higher quality.
A specialist can delegate an available step to AI, and the next person can see the outcome in the same task. Shared context helps hand over work without forwarding private conversations from individual AI accounts.
A management overview is useful when you can move from it to a specific issue. Sembot connects work organisation with the marketing tools people and agents use to complete tasks.
Move from a project comparison to a report and the data for a selected campaign. Inspect ads, URLs and budgets in context. The same data scope helps prepare both the client conversation and the specialist’s next action.
Connect catalogue data with campaign and asset preparation. The team can work on product titles and attributes, ads, images, clips and page descriptions. A shared product offer provides the reference for reviewing content before use.
An issue can originate in a campaign, a product or a task from Asana or ClickUp. Define the process and response: email, SMS, Twilio or a supported action. A shared portfolio queue helps keep track of issues across tools and clients.
AI works with task data, and its output stays attached to the issue. A specialist can request analysis or delegate an available action; the next person inherits the context. Kanban, list and timeline organise execution separately from the portfolio owner’s overview.
Portfolio is a paid platform add-on, not a separate plan required for every task. Start with the deployment model, then choose project capacity and client access.
Work in the ready-to-use SaaS application without preparing your own servers. Add a shared overview of projects, alerts and the team. Project count and feed capacity are selected separately; portfolio alone does not increase those limits.
Run Sembot on infrastructure that meets the requirements, including access through a VPN. Use your own API keys for LLMs and video: pay providers directly, with a 0% Sembot markup. There are no licence limits on scale; capacity depends on the environment’s performance.
Historical case studies describe the engagement, solutions used and results within a particular period. They help you understand Sembot’s experience, but are not evidence of the new portfolio module, AI agents or gains in team productivity. Explore those ways of working in the interactive examples first, then assess them on your own project.
No. The same overview helps an internal team managing several stores, brands or projects. The relevant need is shared management, not the company’s organisational form.
A task focuses on a specific issue; the portfolio shows multiple projects and teams from an owner’s perspective. Portfolio management is an add-on to your chosen Sembot model, not a requirement for using every task.
Platform White Label is a separate add-on with an agreed branding and domain scope. If you also need an isolated environment or VPN, consider Professional. White Label CSS has a separate scope.
In the portfolio preview, compare a project, an alert and the team view.
Choose a pilot project, connect its data and assign an owner to its first process.
Review the first task with the team, then choose the portfolio scope in pricing.
Choose a process, connect its source and review the first result. Find package and add-on details in pricing.
