Dock Pickup - Revision history

Jgreco: Initial proofread pass - docs

2021-11-29T19:55:58Z

Initial proofread pass - docs

Jwolbert at 14:33, 21 June 2016

2016-06-21T14:33:41Z

Jwolbert: /* How it Works */

2016-05-27T13:06:59Z

How it Works

Jwolbert: /* How it Works */

2016-05-27T12:58:11Z

How it Works

Jwolbert: /* How it Works */

2016-05-27T12:57:54Z

How it Works

Jwolbert: Created page with "==Overview== What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled. For some of our..."

2016-05-27T12:57:39Z

Created page with "==Overview== What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled. For some of our..."

New page

==Overview==
What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled. For some of our customers, they may returning assets representing several customer accounts may get all lumped together at one location, perhaps a Dock or Central Receiving. The driver picking up those returns would have a really hard time sorting out which assets are being returned from which account.

Our Dock Pickup process can help you sort it all out.

==How it Works==
At the time of Delivery, the customer places special Parent Customer Number barcodes on each asset at the time of delivery, so Customer ID is scanned here.

# Then during the return, the user will click on Dock Pickup
# Scan or Keyin the Parent Customer Number and cick continue
# Then scan the assets which are being returned from few/many of that parent's departments and click continue
# Confirm the number being returned by clicking Yes.
# The operator will be taken back to the main menu.
# When the driver/operator is back within reach of wifi or cell service, they will synchronize their device to send the information to TrackAbout.
'''Note''' No signature is collected during this action.

Here is how the workflow would look using TAMobile6:

[[File:Dock Pickup.png|200px]]:

Upon saving the whole action, the handheld collates the assets by Customer Number. It saves a single return record for each customer, where each record can have 1 to many assets. For the purposes of Dock Pickup, TrackAbout will assume the assets are being returned from the same department to which they were delivered, thereby avoiding accounting adjustments.

It's important to note, no Invoice #s are collected for these deliveries. So, once the delivery records are available on the TrackAbout website, a user can go in and assign invoice #s to all of those delivery tickets.

==Setup and Configuration==
Dock Pick up is part of the [[Core Tracking]] Module and can be turned on with a request to your [[Contact Us|TrackAbout Support]] Team.

==Notes==

← Older revision		Revision as of 14:33, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Parent Module=Core Tracking
		+	\|Feature Description=A feature to handle returning assets representing several customer accounts
		+	\|Supported In=TAMobile 5, TAMobile 6 Desktop, TAMobile 6 Rugged
		+	}}
	==Overview==		==Overview==
	What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled. For some of our customers, they may returning assets representing several customer accounts may get all lumped together at one location, perhaps a Dock or Central Receiving. The driver picking up those returns would have a really hard time sorting out which assets are being returned from which account.		What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled. For some of our customers, they may returning assets representing several customer accounts may get all lumped together at one location, perhaps a Dock or Central Receiving. The driver picking up those returns would have a really hard time sorting out which assets are being returned from which account.

← Older revision		Revision as of 13:06, 27 May 2016
Line 17:		Line 17:
	Here is how the workflow would look using TAMobile6:		Here is how the workflow would look using TAMobile6:

−	[[File:Dock Pickup.png\|~~800px~~]]:	+	[[File:Dock Pickup.png\|1000px]]:

← Older revision		Revision as of 12:58, 27 May 2016
Line 17:		Line 17:
	Here is how the workflow would look using TAMobile6:		Here is how the workflow would look using TAMobile6:

−	[[File:Dock Pickup.png\|~~400px~~]]:	+	[[File:Dock Pickup.png\|800px]]:

← Older revision		Revision as of 12:57, 27 May 2016
Line 17:		Line 17:
	Here is how the workflow would look using TAMobile6:		Here is how the workflow would look using TAMobile6:

−	[[File:Dock Pickup.png\|~~200px~~]]:	+	[[File:Dock Pickup.png\|400px]]:

@@ Line 5: / Line 5: @@
 }}
 ==Overview==
-What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled.  For some of our customers, they may returning assets representing several customer accounts may get all lumped together at one location, perhaps a Dock or Central Receiving.  The driver picking up those returns would have a really hard time sorting out which assets are being returned from which account.
+What happens when you're dealing with Universities or Hospitals in which deliveries and returns to various departments can easily get scrambled? For some of our customers, they may have returning assets representing several customer accounts getting all lumped together at one location -- perhaps a Dock or Central Receiving. The driver picking up those returns would have a really hard time sorting out which assets are being returned from which account.
 Our Dock Pickup process can help you sort it all out.
 ==How it Works==
-At the time of Delivery, the customer places special Parent Customer Number barcodes on each asset at the time of delivery, so Customer ID is scanned here.
+At the time of Delivery, the customer places special Parent Customer Number barcodes on each asset, so Customer ID is scanned here.
-# Then during the return, the user will click on Dock Pickup
+# Then during the return, the user will click on Dock Pickup.
-# Scan or Keyin the Parent Customer Number and cick continue
+# Scan or Key in the Parent Customer Number and click continue.
-# Then scan the assets which are being returned from few/many of that parent's departments and click continue
+# Then scan the assets which are being returned from few/many of that parent's departments and click continue.
 # Confirm the number being returned by clicking Yes.
 # The operator will be taken back to the main menu.
-# When the driver/operator is back within reach of wifi or cell service, they will synchronize their device to send the information to TrackAbout.
+# When the driver/operator is back within reach of WIFI or cell service, they will synchronize their device to send the information to TrackAbout.
 '''Note''' No signature is collected during this action.
@@ Line 25: / Line 25: @@
-Upon saving the whole action, the handheld collates the assets by Customer Number. It saves a single return record for each customer, where each record can have 1 to many assets. For the purposes of Dock Pickup, TrackAbout will assume the assets are being returned from the same department to which they were delivered,  thereby avoiding accounting adjustments.
+Upon saving the whole action, the handheld collates the assets by Customer Number. It saves a single return record for each customer, where each record can have 1 to many assets. For the purposes of Dock Pickup, TrackAbout will assume the assets are being returned from the same department to which they were delivered, thereby avoiding accounting adjustments.
-It's important to note, no Invoice #s are collected for these deliveries.  So, once the delivery records are available on the TrackAbout website, a user can go in and assign invoice #s to all of those delivery tickets.
+It's important to note that no Invoice #s are collected for these deliveries. So, once the delivery records are available on the TrackAbout website, a user can go in and assign invoice #s to all of those delivery tickets.
 ==Setup and Configuration==