I recommend that all the information that is needed for each new site is correctly documented and added to the Root Active Directory through the Active Directory sites and services. This is done so that the Root AD will automatically build the intersite replication topology based on the information provided about the new site connections. Each new site AD will have an individual domain controller that is known as the intersite topology generator and they are assigned to build the topology at their sites.
For Branch 1 recommendations I would suggest: a site-link protocol of Remote Procedure Call (RPC) over Internet Protocol (IP), a replication schedule/frequency of every 6 hours, starting at 0600 daily, and also having a 56k POTS line for a redundant backup line.
Having a redundant 56k POTS line would be justified because if the main ISP T1 lines should have any issues, dial-up would still provide a way to update the servers. Since Branch 1 has a Call Center with a high employee turnover it is important that there are some means of connection in case an employee is terminated or their account needs to be updated across the domain.
For Branch 2 recommendations I would suggest: for the site-link protocol RCP over IP, for the replication schedule/frequency, once a day at 1900 when most clients are done for the business day and bandwidth will not be impeded upon.
Since Branch 2 is in a remote location and is already utilizing a 56k POTS line system I would recommend that the company invest in satellite internet service either as a main source of telecommunications link or as a redundant line. It would be more cost effective if the company used the satellite connection only for redundancy purposes.
Some rules of thumb in Site and Replication Topology Design
Active Directory site topology maps to the WAN topology of the organization in most cases
Create one site per WAN location, if possible.