CRM

CRM Configuration

The CRM settings section allows operators to configure the various communication channels used to engage with players (Email, Push, On-Site) and manage safety nets for budget and testing.

Path: Settings > CRM

1. Email Configuration

Configure the sender identity and visual templates for system emails.

  • From Email: Enter the email address that will appear as the "Sender" in the player's inbox (e.g., [email protected]).

  • Reply to: Enter the email address where player replies will be sent (usually a support address, e.g., [email protected]).

  • Styles: Click Change to configure the CSS/HTML styling of your email templates to match your brand guidelines.

  • Translations: Click Change to manage localized email content for different languages.

2. Email Styling (Theme)

This section allows you to define the global visual identity for your CRM emails using a configuration editor. You can define colors, fonts, and logos to ensure all outgoing communication matches your brand.

  • Access: Click Change next to Styles in the Email section.

  • Configuration:

    • Theme: Defines the base color scheme (e.g., "dark" or "light").

    • Colors: Click the color box next to fields like fontColor or primaryColor to open a color picker, or enter the Hex code directly.

    • Typography:

      • fontFamily: Define the font stack (e.g., 'Roboto', 'Verdana', sans-serif).

      • googleFontUrl: You can import web fonts directly from Google Fonts to ensure consistent rendering.

    • Logo:

      • src: The direct URL to your brand logo image file.

      • label: The alt-text description for the logo.

  • Important Note: This editor uses a strict syntax. Ensure you do not accidentally delete commas , or quotation marks " when editing text, as this may break the template.

  • Save: Click Update to apply the new theme.

3. Email Translations (Footer & Legal)

This section manages the localized text found in the footer of your emails, such as legal disclaimers, unsubscribe links, and copyright notices.

  • Access: Click Change next to Translations in the Email section.

  • Structure: The content is organized by language code (e.g., en for English, es for Spanish).

  • Editable Fields:

    • license: The regulatory text displaying your license number and jurisdiction.

    • copyright: The copyright year and holder text.

    • terms & termsUrl: The link text and destination URL for your Terms & Conditions.

    • unsubscribe & unsubscribeUrl: The mandatory link allowing players to opt out of communications.

  • Adding a Language: To add a new language, copy an entire block (e.g., the whole en: { ... } section), paste it below, rename the key (e.g., to de), and translate the values inside the quotes.

4. Web-Push Notification

  • Push Notifications Enable: Toggle this switch to Enable or Disable the web-push notification capability globally across the platform.

Based on the detailed screenshots for the styling and translation configurations, here is the continuation of the CRM section of your Operator's Manual.

These sections involve editing code-like structures (JSON/CSS). I have added specific notes to ensure operators handle the syntax carefully to avoid breaking the layout.

5. On-Site Notification Styles

This interface allows you to customize the visual appearance of the "Toast" or "Popup" notifications that appear while a player is browsing your site.

  • Access: Click Change next to Styles in the On-Site Notification section.

  • Preview Pane: The right side of the window shows a real-time preview of a notification (Title, Body, Button, Image) so you can see your changes immediately.

  • Configuration Sections:

    • Basic CSS: Use this section for standard adjustments like background colors, border radius, and font sizes.

    • Extra CSS: Use this section for advanced custom styling if you need specific visual effects or overrides.

  • Save: Click Update to publish the new design to the live site.

6. Push In-App Notification

Configuration for mobile app notifications, typically integrated via OneSignal.

  • One signal enable: Toggle to enable integration with the OneSignal push provider.

  • One signal config: Click Update to enter your OneSignal API keys and App ID.

  • Push In-App URL Domains: Click Update to whitelist specific domains. Links matching these domains will open directly inside the app (deep linking) rather than launching an external web browser.

7. General

  • Test account player IDs: Click Change to manage a list of Player IDs designated as "Test Accounts." These accounts are often used to preview CRM campaigns safely without affecting real players.

8. CRM Budget Alerts

This section acts as a safeguard to prevent overspending on communication providers (Email/SMS gateways). The system monitors usage and sends alerts when volume hits 80%, 95%, and 100% of your defined limit.

  • Monthly max email threshold: Click Change to set the maximum number of emails allowed per month (e.g., 1,000,000).

  • Monthly max SMS threshold: Click Change to set the maximum number of SMS messages allowed per month.

  • Block deliveries on max: Click Change to configure the system behavior when the limit is reached. You can choose to automatically stop sending messages to avoid overage fees.

  • Budget emails for alerting: Click Change to enter the email addresses of the internal staff who should receive these budget warning alerts.

  • Country codes allowed for SMS: Click Change to restrict SMS delivery to specific country codes (e.g., allowing +41 for Switzerland but blocking high-cost international destinations).

PreviousGamificationNextWidgets

Last updated

Was this helpful?