# Step 1 – Basic Company Info

In Step 1 of the Setup Wizard, the company owner provides the foundational information that identifies the company in Carrier and across all external-facing documents.

***

### Required Fields

<table><thead><tr><th width="200">Field</th><th width="90" align="center">Required</th><th>Description</th></tr></thead><tbody><tr><td>Company Name</td><td align="center">✅</td><td>Legal or operational name</td></tr><tr><td>Street Address</td><td align="center">✅</td><td>Main office location</td></tr><tr><td>City, State, ZIP</td><td align="center">✅</td><td>Linked to company timezone and regional settings</td></tr><tr><td>Country</td><td align="center">✅</td><td>Used for compliance modules</td></tr></tbody></table>

***

### Optional Fields

| Field        | Description                       |
| ------------ | --------------------------------- |
| MC Number    | For FMCSA-registered carriers     |
| DOT Number   | Used for regulatory documentation |
| EIN          | Internal Tax ID                   |
| Company Logo | Displayed in invoices and exports |

***

### Behavior

* This step must be completed before continuing
* Address fields support Google address autocomplete
* EIN/MC/DOT numbers are optional but encouraged if applicable

***

<figure><img src="/files/I4lvc3ygJzGf3jbS7mDw" alt=""><figcaption><p><em>Figure: Basic company information fields in Step 1.</em></p></figcaption></figure>

***

> ✅ Tip: Make sure the company name and logo are professional—they appear in invoice headers and email templates.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rute.gitbook.io/carrier/company/settings/setup-wizard-first-login/step-1-basic-company-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
