Field Guide

Set up your revenue sync layer

A practical, technical walkthrough — from first login to live sync rules. Field names and examples are shown in mono type.

Getting started

AlloySync Core is the revenue data sync layer that keeps billing, CRM, support, and product data aligned. Setup follows four moves: connect your tools, map the fields you care about, define routing rules, then watch revenue events flow through Sync Command.

  1. Open the Access Console and sign in to Sync Command.
  2. Connect your billing and CRM tools.
  3. Map the fields that should stay in sync.
  4. Add a rule and confirm events route as expected.

Accessing Sync Command

The software workspace is reachable from the Access page. For evaluation, frontend test access is available.

# Access Console
username test
password test

After signing in you land on the Overview, with sync health, open conflicts, failed payments, upgrades, and active workflows at the top.

Connecting tools

Open Connectors and toggle a tool on to connect it. Each connector has a sync direction you can cycle between two-way, inbound, and outbound.

Billing System  two-way  // invoices, charges, dunning
CRM        two-way  // accounts, deals, owners
Support Desk  inbound  // tickets, escalations

Mapping fields

Open Field Map to connect a source field to a destination field. Each mapping has a type so values are converted correctly.

billing.status  →  crm.account_health  (enum)
billing.mrr    →  crm.deal_value    (currency)
billing.owner  →  crm.account_owner (string)
Disable a mapping instead of deleting it to pause a field without losing its configuration.

Creating sync rules

Open Rules and create a rule with a trigger and an action. Rules decide which events route where.

# Rule
when invoice.payment_failed
then assign + alert account owner
  1. Choose a trigger event.
  2. Define the action — assign, alert, or write a field.
  3. Enable the rule and watch it apply to new events.

Reviewing conflicts

When two systems disagree on a field, the event appears in Conflicts. Review both values and choose the authoritative source — AlloySync Core never overwrites silently.

account_health
  Source A  At risk  (Billing)
  Source B  Healthy (CRM)

Setting alert thresholds

Open Alerts to define a threshold and the channel that should receive it. Separate routes keep billing, CS, and ops focused.

Failed payment  threshold ≥ 1  →  #revenue-alerts
High-value churn  MRR ≥ $500  →  #cs-team

Exporting records

Open Exports, pick a dataset and range, and generate a CSV. You can also import customer records by uploading a CSV in the same view.

# Export
dataset revenue_events  range last_7_days  format csv

Managing team roles

Open Team to invite users and set roles. Roles control who can change connectors, rules, and records.

Owner    full control
Admin    manage settings + members
Operator manage records + rules
Viewer   read-only

Troubleshooting declined checkout (test mode)

The checkout currently runs in transparent test mode. Every payment attempt returns a declined message and no card data is processed or stored. This is expected behavior during evaluation.

To complete a purchase, contact support. Your statement descriptor will read ALLOYSYNCCORE.

Support

Need a hand? Reach the team and we'll help with access, setup, or checkout.

email  support@alloysynccore.com
phone  (385) 446-6318
Contact supportOpen Sync Command