FAQ

The platform uses Two-Factor Authentication (2FA). The first time you log in — or whenever you sign in from a new device — a verification code is sent to your email to complete the validation.

The dashboard is divided into three areas:

• Channels — build a journey or open a standalone platform.
• Recommendations — contextual solutions suggested for your account.
• Analytics — a quick historical overview of your recent campaigns.

Open the top menu bar, click your name and email icon, and go to the Profile section.

Use the "Your projects" dropdown selector in the top menu of the console.

It's the central space where marketers find playbooks and tutorials, and developers retrieve API and SDK reference materials.

From the top menu, click your user profile and select "Plan and billing".

Complete the project requirement configuration and upload the necessary server keys in the project settings panel before launching any channel.

Navigate to Tools > AppPush/WebPush > Web Analytics in the left-hand sidebar.

They can be added as a "Hash" (using the # character) or as a "Query-String" (using the ? character).

Fixed (static) values, or dynamic variables such as Campaign title, Campaign name, Creation date, Platform, Send type, or Category.

Choose the "Multi-Step Journey" template to build multi-channel communication paths with connectors.

In the journey panel, click the blue "Create New Journey" button at the top-right of the screen.

It's a mandatory text value set during configuration. It's used to track statistics and to map each user's path correctly within Data Extensions, so it must be unique and consistent.

A decision split compares the exact label text and routes users down different paths depending on whether they match the criteria.

We recommend externalCode (your unique, encrypted user identifier) over the more volatile deviceId.

Yes. A Multi-Step Journey lets you combine and sequence nodes such as Push, In-App/In-Web, SMS, and Chat within a single automated flow.

Behavioral attributes such as ButtonClicked or UniqueCampaignLabel, and actions such as click or sent.

It links your core customer records with real-time behavior, triggering automated multi-channel campaigns based on specific data attributes.

Link the journey's entry point to targeted contact lists or to synced data definitions managed in the platform.

Yes. Search for the journey in the interface, select it, and modify its steps or update the communication paths.

It's the dedicated workspace for building, configuring, and optimizing generative-AI conversational agents.

They implement the Model Context Protocol (MCP), an open standard that lets the agent integrate in real time with external data, internal APIs, databases, and local files.

A setup that combines autonomous AI reasoning with human customer care, handing complex interactions over to live agents seamlessly.

Yes. It has native multilingual capabilities that break down language barriers automatically during live chat sessions.

By configuring custom webhooks and URL-reading rules directly in the agent's integration settings.

The console provides response security filtering and a temporary-ban blacklist to keep conversations safe.

Through interactive assistance components, including automated emoji-based feedback collected at the end of a chat.

Yes. It supports full rich media, sending multimedia files and interactive elements directly to the user.

AI-powered reporting provides deep analysis of conversation patterns, resolution tracking, and link performance.

They store demographic, structural, and behavioral attributes linked to an individual profile, enabling micro-segmentation.

A deviceId identifies a single app install or browser. The externalCode is the master encrypted key that unifies several devices under one customer identity.

They are relational data sets used to search, isolate, and verify the customer records needed to launch targeted campaigns.

In the Segments menu, where you apply filtering rules against stored fields and logged user actions.

It correlates your external CRM contact keys with indigitall identifiers in real time, preventing disconnected or duplicated profiles.

A tool that automatically adds or removes contacts from specific interest categories based on their deviceId or externalCode.

It queries your designated Data Extensions to match the exact profile and check whether the user qualifies for a custom message.

Yes. Behavior across all channels — clicking a push, opening an email, and so on — is logged on the same profile and can be used as a segmentation filter.

In the Customer Data Platform sub-menu, under CDP / Customer Fields.

It feeds live contact variables and mapped attributes directly into your message templates as dynamic text placeholders.

A suite of tools that lets brands build digital stores and interactive shopping paths directly inside WhatsApp, using Meta's Commerce Manager.

A structured digital repository where you hold and organize all the inventory items you want to display or sell inside messaging apps.

Choose "Connect a partner platform" during setup so Meta can sync product details automatically with tools like Shopify.

The platform natively supports Single-Product and Multi-Product message templates.

You must fill in the Project name, Template ID, Namespace, Language code, and the target Contact field.

You can configure variables for the Header, Body, Footer, and interactive CTA or Quick Reply buttons.

Both values are listed on the detail screen of your approved template inside the console.

Install the free indigitall plugin on your web environment to manage and deploy the chat widget.

Its screen alignment (left/right), colors (via RGB, HSL, or HEX), a default layout, or a custom graphic you upload.

It sets how many seconds the system waits before showing the WhatsApp icon after a visitor arrives. Setting it to 0 displays it instantly.

Through a Canvas application that embeds the entire communication platform directly inside the Salesforce console workspace.

A direct link to the user's master profile, so they can edit it immediately without leaving the chat.

The integration creates a case automatically and brings the live WhatsApp conversation history into the CRM ticket.

They fill out a fully configurable form embedded inside the active chat window, mapping the data directly to the case file.

A unified inbox supports apps, websites, WhatsApp, Instagram, Facebook Messenger, and custom connected endpoints.

In a hybrid workspace: the AI agent fields incoming interactions and hands the active context over to a human operator when required.

Under Contact Center / Configuration in the main menu.

Yes. The embedded forms are fully configurable, so you can change which parameters are captured per queue.

The Canvas application connects directly to the CDP to pull previous touchpoints, web activity, and message responses.

It removes software silos — agents manage omnichannel conversations, review histories, and update CRM records without leaving a single screen.

Under Tools > AppPush/WebPush > Web Analytics in the left navigation menu.

Google Analytics and Adobe Analytics are officially supported for tracking notification performance.

The Key name, the Value type (fixed or variable), the target Platform (app-push, web-push, or both), and the URL Location.

In the "Hash" zone (after a # character) or in the "Query-String" zone (after a ? character).

It dynamically inserts unique parameters into the link, such as Campaign title, Campaign name, Creation date, Platform, Send type, or Category.

The console automatically concatenates your assigned keys using the standard & separator, based on your rule configuration.

Fixed values append the same tracking text to every notification for general channel sorting. Variable values insert dynamic parameters that are unique to each campaign.

You can drop an App Push or Web Push node directly into any step of a HubSpot workflow.

Paste the Campaign ID generated in the indigitall console, then choose your device lookup method (deviceId or externalCode).

The complete structure is available under the "Dev Guide" and "API" tabs in the console.

They refer specifically to the inWeb (in-website) and inApp (in-application) native engagement toolkits.

The targeted Application project, your verified Audience Search definition, and the appropriate Data Extension.

No. They display natively within the interface during an active session, so no opt-in permission is required.

Apply filters that match the active session against pre-compiled segment lists and properties stored in the CDP.

They let the system look up, retrieve, and map the precise user attributes needed to display personalized layouts.

Impression volumes, view tracking, and call-to-action clicks are recorded in the standard analytics reporting panels of the console.

Yes. Map any customer property from your designated Data Extension to appear dynamically inside the layout.

It delivers rich visual engagement — modals or embedded banners — to active visitors without relying on external browser delivery channels.

Under the "In-App / In-Web Toolkit" sidebar option, or within your campaign creation tools.

Yes. Drag the custom-solution node into a Multi-Step Journey to display content when a contact reaches that specific milestone.

You must define the campaign label, assign the telephone database lookup source, and identify your contact data configuration.

Drag the indigitall SMS connector node into your HubSpot workflows to fire immediate text updates based on contact events.

We highly recommend routing text messages with externalCode to maintain unified profile tracking.

Yes. The body copy can incorporate dynamic attributes pulled from your synchronized contact Data Extensions.

In the SMS workflow dashboard, or directly inside the core multi-channel campaign creation panel.

Yes. Configure decision paths to trigger an SMS automatically if a user doesn't interact with an email or push notification within a given time.

Make sure your audience lists correctly map phone country codes and local number fields into the integration.

Total sent volumes, delivered counts, and failure reports update in real time within the console's analytics interface.

Yes. High-throughput transactional SMS tools are available and fully documented in the developer API guides.

Yes. Links contained in your SMS copy can be tracked by applying keys through the console's Web Analytics panel.

It's the dedicated staging and operational environment in the indigitall Hub used to build, test, and launch Rich Communication Services campaigns.

Media-rich layouts, structured visual content, and interactive text components that are native to mobile operator networks.

Yes. It has its own interface, labeled "RCS Sandbox", under the core channel navigation directory.

All developer methodologies, structured scripts, and OpenAPI endpoint paths are hosted in the "Dev Guide" and "API" tabs.

It operates alongside channels like WhatsApp and Push, letting you send interactive visual sequences and collect responses within a single framework.

Yes. The RCS channel can be embedded within Multi-Step Journeys to run highly contextual, visual messaging campaigns.

Yes. You can apply Google Analytics or Adobe Analytics tracking to links inside RCS content using the global Web Analytics panel.

To deliver app-like visual interactivity and rich media directly inside native text messaging — without forcing customers to download an application.

Yes. The platform isolates RCS analytics from standard text channels to give you accurate reporting on rich-media engagement.

From the main landing view, under the "Channels" selection area.

Go to the user configuration area, which you can reach either from the Projects menu (cogwheel icon) or via the User configuration menu.

In the Email configuration menu, click "New", fill in the domain name along with your domain parameters, and save.

All established domains appear in a central list, where you can modify or remove them using the dedicated "Edit" and "Delete" buttons.

Select your domain in the left-hand area, click "Edit", click "New", and enter the Sender display name along with the Username (the email address).

Yes. Once your main domain is established, you can reuse the creation tool to register several distinct senders.

It displays all the technical authorization records and DNS configurations your email service provider needs to approve the integration.

Email template building and asset management live in the Email Marketing area, or you can design them directly within the Multi-Step Journey canvas.

To guarantee that all security records, domain keys, and validation parameters are correctly copied to your domain provider for verification.

Drag and drop the email channel activity into a Multi-Step Journey and link it to your verified domain and sender username.

Yes. Links inside your email templates can be automatically appended with custom UTM tracking codes using the console's Web Analytics rules.

It's a channel environment dedicated to establishing and managing a persistent internal message center or notification box within apps or sites.

It builds a dedicated message-history center inside the brand's application, where alerts and rich content are stored so they don't disappear.

Yes. It is explicitly listed as its own workspace under the "Channels" directory on the console homepage.

Yes. Campaign playbooks let you fire a live push notification while simultaneously preserving the text payload inside the user's Inbox workspace.

The structural API commands, fetch rules, and UI data-mapping scripts are located in the "Dev Guide" section of the portal.

Yes. Inbox campaigns can be micro-targeted to clear-cut audience definitions or relational Data Extensions compiled in the CDP.

It ensures critical updates, coupons, and transactional notices stay permanently accessible — even if the user accidentally clears their system push history.

Yes. The integrated SDK tracks message engagement and logs read statuses directly into the console analytics dashboard.

Yes. It delivers message data in clean structures, so apps can safely render images, detailed descriptions, and links according to their native design.

Launch the setup process from the indigitall Hub homepage, under the "Inbox Workspace" directory.

The verified platforms are Salesforce Marketing Cloud, Salesforce Service Cloud, HubSpot, VTEX IO, WordPress, Microsoft Teams, Google Analytics, and Adobe Analytics.

It embeds the indigitall Contact Center and a generative-AI conversational bot directly into the Salesforce console using a secure Canvas app frame.

Installed from the HubSpot App Marketplace, it lets you integrate App Push, Web Push, SMS, and WhatsApp nodes into your standard HubSpot workflows.

It's a free module from the WordPress dashboard that lets non-technical users configure WhatsApp Instant Chat widgets and Web Push notifications in one place.

You only need a standard Microsoft Teams administrator account to follow the step-by-step connection guide in the documentation.

It integrates as an automated conversational assistant, interacting with users across internal business communication spaces.

Google Analytics and Adobe Analytics are officially supported to receive campaign parameter data from notification links.

It connects indigitall's multi-channel communication engine to the VTEX digital commerce framework to power automated store notifications.

No. The connectors are pre-built to link up with these tools without costly or complicated engineering work.

Under the "Technology Partners" segment of the documentation home menu, inside the "indigitall & Partners" workspace.