Skip to main content
Fortics Chat Center (formerly SZ.chat) is Fortics’ omnichannel customer service platform: WhatsApp, web chat, Instagram, Telegram and other channels in one place, with chatbot flows, teams of agents and attendance reports. This connector brings the finished attendances with their messages, the monthly attendance report, the contacts and the registers you need to read them: agents, administrators, teams, channels, tabulations, tags, user groups, pauses, time groups, contact groups and predefined messages.
The connector only reads data. It never creates, changes or deletes anything in Fortics Chat Center.

Configuring Fortics Chat Center as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Fortics Chat Center option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The connector signs in to your Fortics Chat Center instance with the e-mail and password of a user, the same ones used to sign in to the web app. Use an administrator (Settings > Administrators) that signs in with a password, not through single sign-on. We recommend a user created for Nekt, so that a password change by a person does not stop your syncs. The following configurations are available:
  • Fortics Chat Center URL: The address you open Fortics Chat Center with, for example https://yourcompany.sz.chat. Only the address of your instance is used, and it must start with https://.
  • E-mail: Login e-mail of the user.
  • Password: Password of that user.
  • Start Date: Earliest date of the attendances, messages and monthly reports read on the first sync. Registers (contacts, agents, teams and the others) are always read in full.
  • Attendance Lookback (days) (advanced, default 3): Days before the last sync that are read again on every sync, so attendances that finish or change late are updated. Use 1 to 31.
An agent user (instead of an administrator) can be refused some tables, such as the monthly attendance report, and may not be able to sign in outside its working hours. Tables the user cannot read are skipped with a warning naming them; the others still load.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data. Attendances, their messages and the monthly report are incremental.
    • Full table: every time the extraction happens, we’ll get the current state of the data. Contacts and the registers are always read in full.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. Fortics Chat Center keeps attendance history only for the storage period of your plan, so a full sync of Attendances or Attendance Messages reloads only what Fortics still keeps; older rows leave the table. Prefer the incremental sync for these tables.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.

Fields by stream

Every table also has an extra_fields column (JSON) with any other field Fortics Chat Center returned for the record. Credentials (tokens, passwords, keys) are never loaded.

Attendances

Finished attendances (conversations handled by the bot or by an agent), one row per attendance, with the team, agent, channel, contact, tabulation, tags, events and the waiting and handling times. Attendances in progress appear after they finish.Table: attendances · Primary key: id · Sync: Incremental
Every message of each finished attendance: who sent it (contact, agent or bot), its type and text, and when it was sent.Table: attendance_messages · Primary key: attendance_id, message_id · Sync: Incremental
Fortics’ attendance report (“Atendimentos Business”) per month, channel, team and agent: number of attendances, messages and HSM (WhatsApp template) messages. Requires an administrator user.Table: attendance_report_monthly · Primary key: month, channel_description, campaign_name, agent_login, agent_name · Sync: Incremental

Contacts

Every contact of your Fortics Chat Center, with their identifiers on each platform and their contact groups.Table: contacts · Primary key: id · Sync: Full table
Contact groups used to segment contacts.Table: contact_groups · Primary key: id · Sync: Full table

Team and operation

Agents (attendants), their teams, working hours and permissions.Table: agents · Primary key: id · Sync: Full table
Administrators of the instance and their permission profile.Table: admins · Primary key: id · Sync: Full table
Teams (“Equipes”; called campaigns in the Fortics API) with their agents, tabulations, tags and attendance rules.Table: teams · Primary key: id · Sync: Full table
User groups (permission profiles).Table: user_groups · Primary key: id · Sync: Full table
Pause types agents can take.Table: pauses · Primary key: id · Sync: Full table
Business-hours groups used by flows and teams.Table: time_groups · Primary key: id · Sync: Full table

Channels and classifications

Service channels (WhatsApp numbers, web chats, Telegram bots, Instagram and others). Channel credentials are never loaded.Table: channels · Primary key: id · Sync: Full table
Tabulations: the classifications (closing reasons) an agent gives when an attendance ends.Table: tabulations · Primary key: id · Sync: Full table
Tags agents put on attendances, and the teams that may use each one.Table: tags · Primary key: id · Sync: Full table
Predefined (quick reply) messages.Table: predefined_messages · Primary key: id · Sync: Full table

Implementation notes

  • Attendances are finished attendances. Fortics lists attendance history by date; an attendance in progress appears in Attendances (and its messages in Attendance Messages) once it finishes. Each sync lists the last 31 days (90 days when Fortics lists attendances by their start date) and loads the attendances that finished since the previous sync (plus the days of Attendance Lookback), so attendances that stay open for several days are still captured when they finish. An attendance open for longer than that may not be loaded.
  • Teams are “campaigns” in Fortics. The team of an attendance is in campaign_id and campaign_name; the Teams table has the same identifiers.
  • Monthly report rows. The report has names, not identifiers, so each row is identified by month, channel, team, agent login and agent name; two rows with the same names are loaded as one row with their counts added. If the report changes order while it is read, the month is read again; if it keeps changing, the table is not updated in that sync and the sync log says so. The current and the previous month are read again on every sync. If a channel, team or agent is renamed in Fortics during those months, the row under the old name stays in the table: to sum a month, keep only the rows with the latest extracted_at of that month.
  • Contacts. Contacts are read by creation date and checked against the count Fortics reports. Contacts created during the sync are fine. If contacts are deleted while they are read, the connector reads that period again; if they keep disappearing or the list comes back short, the Contacts table is not updated in that sync and the sync log says so.
  • Times. total_time_seconds, handling_time_seconds and waiting_time_seconds are Fortics’ TTA, TMA and TME of each attendance, in seconds.
  • Dates. Dates are loaded as the text Fortics returns. Record timestamps (created_at, updated_at of the registers) are in UTC; attendance and message times (finished_at, timer_on_wait, message created_at) are in the local time of your instance, named in the timezone column of Attendances.
  • Attendances without details. When Fortics no longer keeps the details of an attendance (after the storage period of your plan), the attendance is loaded with the list fields only (detail_available = false) and without messages, and the sync log says how many.
  • Permissions. Before reading anything, the connector checks that the user can read every table you selected. A table the user is not allowed to read, or that your Fortics instance does not have, is skipped with a warning naming it and saying which of the two happened, and the other tables still load; if the user cannot read any selected table, the sync fails with a message.
  • Rate limits. If Fortics Chat Center asks the connector to slow down, the sync waits and continues, and says so in the sync log.