Figensoft

The FigenSoft Connector integrates the Netmera platform with the FigenSoft SMS gateway service, a provider primarily recognized in the Turkish market for its support of the IYS (İleti Yönetim Sistemi) compliance requirements.

Overview

Attribute	Details
Connector Name	FigenSoft
Category	SMS Providers
Provider Location	Turkey
Primary Function	Outbound SMS delivery, specifically supporting IYS Message Types
Data Flow	Outbound (Netmera > FigenSoft)
Priority Ranking	High (Rank 3, after Message Center and Mobildev)

FigenSoft is a high-priority SMS connector, notable because it supports configurations specific to the Turkish legal framework, allowing different credentials or API behaviors based on whether the message is a Campaign or a Notification.

Use Cases and Benefits

1. IYS Compliance: The most crucial use case is facilitating SMS delivery that complies with the Turkish IYS (Commercial Electronic Message Management System) regulations.

2. IYS Message Type Support: FigenSoft supports the selection of the IYS message type (NOTIFICATION or CAMPAIGN). When an SMS campaign specifies the CAMPAIGN type, the FigenSoft connector ensures that IYS consent checks are performed on the provider's side before sending the message, adhering to legal requirements.

3. Prioritized SMS Routing: As the third-highest priority connector, FigenSoft acts as a reliable channel when the top-ranked providers (Message Center and Mobildev) are unavailable.

Data Flow

The data flow is Outbound, involving Netmera submitting the message payload to the FigenSoft API.

1. Message Creation: A marketer creates an SMS message in Netmera, specifying the IYS Message Type (e.g., CAMPAIGN or NOTIFICATION).

2. Adapter Selection: The Netmera messaging service checks providers based on priority. If FigenSoft is selected, the system attempts to find the appropriate FigenSoft configuration matching the IYS message type specified in the SMS content.

3. API Submission (Conditional):

   • The connector uses the specific configuration (username, password, sender list) corresponding to the message's IYS type.

   • If the message is tagged as CAMPAIGN, the FigenSoft API is expected to handle the necessary IYS consent verification for the recipient's phone number before delivery.

4. Delivery: The message is relayed through the FigenSoft gateway.

Configuration Reference

The FigenSoft connector is unique as it can be configured based on the specific IYS message type, requiring multiple credentials to manage different messaging categories.

Parameter	Type	Description
username	String	FigenSoft API username.
password	String	FigenSoft API password.
smsIysMessageType	String	The IYS message category this configuration serves (NOTIFICATION or CAMPAIGN).
senderList	List	List of approved Sender IDs.
customApiActive	Boolean	Flag to enable the use of a custom API URL.
customApiUrl	String	Custom API endpoint URL (if customApiActive is true).

Setup Instructions

Setting up the FigenSoft integration involves obtaining IYS-related credentials from the provider and configuring matching entries in Netmera.

1. Prerequisites: Establish an account with FigenSoft and complete the IYS integration setup on their platform, ensuring you have approved Sender IDs and API credentials for both Notification and Campaign message types (if managing both).

2. Configure in Netmera: Navigate to the Netmera Connectors section and select FigenSoft.

3. Input Credentials: Input the required credentials (username, password, sender list). Crucially, define the smsIysMessageType (NOTIFICATION or CAMPAIGN) for this specific configuration entry.

4. Custom API (Optional): If a non-standard API is required, set customApiActive to true and provide the customApiUrl.

5. Save: Save the configuration. Repeat the process if you require a separate configuration for the other IYS message type.

Usage Notes & Considerations

1. IYS Type Dependence: The integration relies heavily on identifying the correct IYS message type (NOTIFICATION or CAMPAIGN). If an SMS message specifies an IYS type for which no corresponding FigenSoft configuration exists, the message may fail to send via this connector.

2. Priority Sequencing: As Rank 3, FigenSoft will be bypassed entirely if the higher-priority Message Center or Mobildev connectors are active and successfully processing SMS traffic.

3. Turkish Compliance Focus: The core benefit and complexity revolve around Turkish regulatory compliance. Clients operating outside of the necessity for IYS checking might prefer a simpler, higher-throughput global provider like Infobip or Twilio (though they rank lower).

4. Credential Management: Any changes to the username or password on the FigenSoft side must be manually reflected in the Netmera configuration to prevent immediate delivery failures.