Daktela

Before you startCopy Anchor Link

Sign in to Seflo and ask your Daktela administrator for your instance URL and a user access token. The token must identify the Daktela user whose tickets you want to work on and allow access to that user's open tickets.

Use an HTTPS origin such as https://customer.daktela.com, without /api, another path, a query or a fragment. Enter the token only in the Seflo connection form; do not paste it into an AI conversation.

Connect DaktelaCopy Anchor Link

1. In Seflo, open Sources, then Add source.
2. Choose Continue on the Daktela card.
3. Enter the instance origin in Daktela URL and the user token in Access token.
4. Choose Connect Daktela and review the connection information shown by Seflo before continuing.
5. On the source page, check the instance and connected user before synchronizing work.

Seflo checks the URL, validates the Daktela user and verifies ticket access before saving the connection. Daktela uses the access token for this connection, rather than an OAuth sign-in screen. A saved token is not displayed again.

Verify your first ticketCopy Anchor Link

1. On the Seflo home page, choose the Last synced control to synchronize connected sources.
2. Check the synchronization result. If there is no matching work, confirm that an open ticket is assigned to the connected Daktela user.
3. Open an imported task and check its title, ticket context and original source before asking an assistant to work on it.

Synchronization brings the connected user's open ticket work into Seflo, with ticket descriptions and comment activity. It does not import every ticket in the instance.

Work on a linked ticketCopy Anchor Link

After connecting an AI client, ask it to inspect the task using its Seflo task code. Review the proposed action before sending a comment or handing the ticket to an available Daktela user.

A comment is written to the Daktela ticket. A handoff changes its assignee and can include a comment. Completing the personal Seflo task does not by itself close the Daktela ticket. Available actions depend on current ticket access, status and assignment; see Review actions.

If connection or synchronization failsCopy Anchor Link

• URL rejected: enter only the HTTPS origin, without /api or another path.
• Token rejected: ask your administrator to verify that the token is valid and belongs to the intended user.
• Ticket access denied: check that the user can read the expected assigned tickets.
• No tickets appear: check the connected identity, assignment and ticket status, then synchronize again.
• Source needs attention: follow the source page's reconnect or recovery action. Check the current result before repeating a comment or handoff whose delivery is uncertain.

For broader connection problems, use Troubleshooting. Return to Connect a source to choose another service.