Agent as app

Overview

Agent as app lets you deploy your Swiftask AI agent as a standalone, full-page web application accessible through a dedicated URL. External users and customers can interact directly with your agent without needing a Swiftask account or complex integration setup.

This feature allows you to deliver branded customer-facing experiences, share automated tools across teams, and embed dynamic contextual data. It provides dedicated management tabs for iframe embedding, visual personalization, ownership transfer, and automated credit threshold alerts.

Prerequisites

Before configuring your agent as an app, ensure you have:

• An active Swiftask account with workspace access.

• An existing AI agent configured with instructions, objectives, and any required knowledge sources or skills.

• Admin or Owner permissions on the agent or workspace to modify deployment, ownership, and billing configurations.

• Sufficient workspace AI credits to support external user conversations.

Step-by-step guide

1. Access the agent as app settings

1. Navigate to the Agents section from the left sidebar and select your agent to open its configuration page.

2. In the left panel, scroll down to the Deployment section and click Agent as APP.

3. If public access has not been activated, you will see the Unlock external integration prompt. Click Enable public mode (or toggle the Enable public mode switch in the top-right corner).

2. Preview the standalone application

1. Once public mode is active, click the Open preview button located at the top of the interface.

2. A new browser tab opens displaying your agent's standalone interface, allowing you to test conversations, layout, and visual elements in real time.

3. Configure integration options

Click the Integration tab to choose how you want to embed or share your agent application:

1. Basic integration: Copy the standard <iframe> code snippet and paste it directly into your website or portal HTML where you want the full-page interface to appear.

2. With external context: Use the context-aware <iframe> snippet to pass dynamic user parameters (such as customerName, orderNumber, or productType) as a JSON string within the URL. This allows the agent to deliver personalized responses based on specific session data.

4. Personalize appearance and chat behavior

Click the Appearance tab to customize the visual elements and behavior of the agent app:

1. Under Personalization, set the following interface options:

• Input placeholder: Enter custom placeholder text shown in the chat input field (for example, "Type a message…").

• Welcome message: Define the initial greeting shown to visitors. You can type the message or record it using the microphone icon.

• Accent color: Select your brand accent color using preset color swatches or the custom color picker.

2. Under Starter question, toggle Show floating Starter Questions and click + Add a new startup question to provide pre-built prompts that guide visitors on how to interact with your agent.

3. Under Advanced options, configure the following toggles:

• Enable file reception: Allow or disallow users to upload documents directly into the chat (maximum file size: 5 MB).

• Hide Swiftask branding: Remove the "Powered by Swiftask" badge from the app interface.

• Welcome Message: Show or hide the floating welcome message popover.

• Hide chat history sidebar: Toggle off the sidebar to display only the active conversation area without past sessions.

• Skills display in chat: Click the dropdown to control the visibility of tool executions, thinking steps, and skill blocks.

4. Choose from the three visibility modes for skills:

• Show everything: Displays all skill blocks, tools, and thinking steps.

• Hide skills completely: Hides all behind-the-scenes skill operations from users.

• Show skill title only: Displays the name of executed skills without exposing detailed parameters.

5. Manage cost control and ownership

Click the Cost Control tab to govern administrative responsibility and credit billing:

1. Review the Ownership and billing overview to see the current manager and the account supporting public credit consumption.

2. Note the built-in Cost resolution rules and display priority:

• Priority 1: Designated credit consumer

• Priority 2: Agent creator

• Priority 3: Delegated owner (Owner access)

• Priority 4: Workspace owner

• If the designated consumer or creator leaves the workspace, charges automatically roll over to the next eligible owner.

3. To change the agent's owner, click the pencil icon next to Current owner:

• In the Transfer ownership modal, choose a workspace member from the Select a new owner dropdown.

• Check Transfer also the responsibility of credit consumption to the new owner if the new owner should also support the billing costs. If unchecked, the current consumer continues to pay.

• Click Transfer ownership.

4. To reassign billing without changing ownership, click the pencil icon next to Credit consumption:

• In the Change consumer modal, select the team member from the Select a new credit consumer dropdown.

• Click Change consumer.

6. Set up credit monitoring alerts

Click the Credit monitoring tab to track usage and receive proactive notifications before credits run out:

1. Toggle on Enable credit threshold alerts.

2. In the Credit Threshold field, enter the specific credit usage count at which an alert should trigger.

3. In the Users to notify section, search by name or email to select workspace members who will receive alert notifications.

4. Review the Notification Logs table at the bottom to audit past alerts, including timestamp, notification type, message content, and status actions.

Practical use cases

Customer support portal

Deploy an agent as app on your client portal with product documentation and FAQ sources attached. Customers get 24/7 self-service support, while the "Hide skills completely" setting keeps internal search queries confidential.

Personalized account assistant with external context

Embed the agent inside your SaaS web application using the context integration snippet. Automatically pass customer names, plan levels, and account IDs to provide contextual onboarding and account guidance.

Dedicated recruitment and HR assistant

Share an agent application link on your careers page. Prospective candidates can ask questions about open roles, required qualifications, and interview processes without taking up recruiter time.

Lead qualification tool

Deploy a public agent app to engage website visitors. Configure starter questions like "Schedule a product demo" or "Request a pricing quote" to capture prospect details and route qualified leads.

Tips & best practices

• Test in preview mode first: Always click Open preview after changing your welcome message, starter questions, or accent color to verify formatting before publishing.

• Use external context for personalization: When embedding inside client dashboards, pass unique session parameters in the URL to eliminate repetitive introductory questions.

• Set proactive credit alerts: Configure a credit monitoring threshold below your total workspace budget to receive warning notifications before an agent stops responding.

• Assign a dedicated billing owner: Use the Credit consumption selector to designate an administrative billing account, ensuring team member role changes do not disrupt live agent operations.

• Select the right skill display mode: Use "Show skill title only" or "Hide skills completely" on customer-facing apps to maintain a clean chat stream and prevent exposing technical tool queries.

Troubleshooting

Issue: Users cannot access the agent app URL

• Cause: Public mode has been toggled off or was not initialized.

• Fix: Open the agent settings, navigate to Deployment → Agent as APP, and ensure the Enable public mode toggle is turned on.

Issue: Agent stops responding to public queries

• Cause: The assigned credit consumer account has depleted its AI credits or reached an account limit.

• Fix: Open the Cost Control tab to verify the current credit consumer. Recharge workspace credits or reassign credit consumption to another eligible member.

Issue: External context parameters are not reflected in answers

• Cause: The JSON string passed in the &context= URL parameter is improperly structured or contains unencoded special characters.

• Fix: Verify that the context object follows standard JSON formatting with valid keys and string values, and ensure special characters are URL-encoded.

Additional resources

• Introduction to agents

• Embed and widget

• Share an agent with workspace members (standard sharing)

• Lock agent