The ID of the Customer that the Contact is attached to

The name of the Contact. Example: "John Doe"

Usually the street address. Example: "8653 Fake Street"

Optional second line of address. Example: "Apt 26"

The city of the Contact. Example: "New York City"

The state of the Contact's address. Example: "Connecticut"

The zip or postal code of the address of the Contact. Example: "90065"

The email address of the Contact

The phone number of the Contact

The mobile phone number of the Contact

Any notes about the Contact

The Customer ID is shown in the URL when you go to the Customer Detail page.

The date on the Estimate. If you get an error, try putting your date in quotes.

The note on the Estimate

The ID of the associated Ticket. Enter 0 if no Ticket associated.

The ID of the associated Location

We will use the Phone or Email to find the matching customer in your RepairShopr account.

Defaults to "New".

This is the main body of the "first comment" on the ticket, also referred to as the "Initial Issue" for the ticket.

The subject for the initial issue - generally "Initial Issue" is what you want when you create a Ticket.

If you are a big chain user, you'll want to get a location_id on all new tickets.

Caller phone number, like 14255551212.

The ID of the Customer

The Business Name of the Customer

The first name of the Customer

The last name of the Customer

The email of the Customer

The phone number of the Customer

The mobile phone number of the Customer

The first line of the Customer's address

The second line of the Customer's address (usually an Apartment number or Suite number)

The city of the address of the Customer

The state of the address of the Customer

The zip/postal code of the address of the Customer

Any notes about the Customer

Whether or not the Customer should receive SMS messages

Whether or not the Customer is opted out of marketing communication of all kinds

Whether or not the Customer should be opted out of email of any kind

Whether the Customer should receive billing emails

Whether or not the Customer should receive Marketing Emails

Whether or not the Customer should receive Report Emails

Default answers are: Customer, Google, Sign, Friend, and Other. You may also add Custom answers in the Customer Settings section of Syncro.

If referred by a Customer, the ID of that Customer

The ID of the Tax Rate of the Customer

The email addresses to use for Notifications. Can be a comma delimited list, such as "john@doe.com, jane@doe.com" or just a single email such as "john@doe.com"

Any email addresses to CC on all invoice emails. Can be a comma-delimited list of emails such as "john@doe.com, jane@doe.com"

The ID of the Invoice Terms object associated with this Customer

The subject/summary of the Appointment

The Start Time of the Appointment

The End Time of the Appointment

The description of the Appointment

The type of Appointment. "customer" = Onsite "shop" = Our Office "Phone Call" = Phone Call "customer" = Pick-up "pre_defined" = "Remote Support"

The location of the Appointment

The ID of the Ticket associated with this Appointment

The ID of the User that owns this Appointment

User ID for any additional Users that will be attending the Appointment

Is the appointment an All-Day appointment?

The ID of the Customer associated with this Appointment

First Name of the Customer.

Phone Number is the primary (non-mobile) phone, like home or work.

Mobile Number is the primary mobile phone - which can be used for SMS in RepairShopr.

First line of the address, like: "123 Any Street".

Here you can place a hash/object of data that we will attempt to map to your custom fields.

First Name of the Contact.

Phone Number is the primary (non-mobile) phone, like home or work.

Mobile Number is the primary mobile phone - which can be used for SMS in RepairShopr.

First line of the address, like: "123 Any Street".

A brief issue description - this becomes the "Ticket Subject" when converted from a Lead to a Ticket.

This is the long description with full detail.

Like a category for the problem.

If you want this to tie to a Location in your RepairShopr account, you can specify this.

Here you can place a hash/object of data that we will attempt to map to your custom fields.

The ID of the Ticket that this Ticket Timer should be associated with

When the Ticket Timer started

When the Ticket Timer ended

The ID of the User that performed the work

Any notes related to the Ticket Timer

The ID of the Product associated with this Ticket Timer. Usually a labor Product.

The ID of the Ticket Comment associated with this Ticket Timer Entry

The ID of the Contact

The name of the Contact

The ID of the Customer that the Contact is attached to

The first line of the address for the Contact

The second line of the address of the Contact

The city of the address of the Contact

The State of the address of the Contact

The zip/postal code of the address of the Contact

The email address of the Contact

The phone number of the Contact

The job title of the Contact

The mobile phone number of the Contact

Any notes about the Contact

The ID of the Ticket

The ID of the Ticket Custom Field Type of the Ticket

The Ticket Number of the Ticket

The subject of the Ticket

The due date of the Ticket

The ID of the location of the Customer of the Ticket

The problem type of the Ticket

The status of the Ticket

The ID of the User this Ticket is assigned to

The Priority of the Ticket

The ID of the Contact associated with the Ticket

The ID of the SLA associated with the Ticket