---
title: "Creating a Comm Type"
canonical: "https://docs.rubiconwater.com/space/CFGNC/2018672670/Creating%20a%20Comm%20Type"
format: markdown
---
> Macro (toc)

Create a comm type to send messages of a particular type to any registered recipients.

> ℹ️ **Note**
> ℹ️ 
> ℹ️ Once you have configured a comm type, you can use it to send messages using the <u>[Customer Comms Module](https://rubiconwater.atlassian.net/wiki/spaces/MSGNC/pages/2008645633)</u>.

**Step 1**

In the Comm Types module click **Add** to create a new comm type

**Step 2**

Enter the following details:

| **Field** | **Description** |
| --- | --- |
| Name | Enter a Name for the comm type, for example: "Water Restrictions" |
| Registration Enabled | Make the comm type active. This is typically enabled so that customers can be registered for comm types. It is only disabled for communications that are not intended for customers (such as meter reading export files). |
| Default message | Enter a default message for this comm type. You will have the opportunity to change or replace this when you create messages. |

**Step 3**

Configure the Registration options:

Specify whether you want user registrations to default to *Mandatory*, *Opt in* or to *Opt out*.

- If the comm type is *Mandatory* it will be sent to all users and they will not have the option to opt out.
- If the users must *Opt in*, they must specifically pick this comm type in order to receive messages.
- If they must *Opt out*, they will automatically be registered for this comm type (provided it is available for them), but they can opt out if they choose.

Specify whether this comm type is intended for OWNERS or OPERATORS (or both).

**Step 4**

If you want to restrict the comm type to specific groups, you can do this in the Groups section. See <u>[Restricting Communications to a Group](https://rubiconwater.atlassian.net/wiki/pages/createpage.action?spaceKey=MSGNC&title=Restricting%20Communications%20to%20a%20Group)</u> for more details.

**Step 5**

In the **Delivery Method** section, specify what communication methods (such as sms, email, fax, push notification, or publish to portal) the comm type will use and what the priority of each method will be.

> ℹ️ **Note**
> ℹ️ 
> ℹ️ Push notifications are a type of App Notification and can be received by users of NetworkConnect, SiteConnect, and CustomerConnect. See [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3572039699](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/3572039699) for more details.

For each communication method in the table:

1. Double-click the method row or select it and click Modify.
2. In the **Modify Details** screen, select **Enabled** to use the delivery method with the comm type.
3. Enter a **Priority** (1 is highest, 3 is lowest). Each method must have a different priority.
4. Click **OK**.

If a customer is registered to receive messages by more than one method, the message will only be sent by the method with highest priority.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ You might prioritise email delivery over sms delivery if you intend to send messages that include attachments. Attachments are not sent with sms messages.

**Step 6**

Click **Save** to save your changes.

# How often does a Comm Type run?

A Comm Type runs at regular intervals and checks whether the conditions for sending an alert are met. The frequency value in seconds is given by the *Poll Period* attribute value on the Comm Type object. The default is 120 seconds.

---